Hi,
I have created an installation msi for my application using Advanced Installer version 7.3.1. Unfortunately I am having difficulties under Windows 7.
After my application has installed to C:\Program Files\Darren Link\ApplicationName my application gets an access denied error when the executable file tries to write a configuration file to this directory. The defult configuration files are created on first run, rather than being distributed with my application. My application is written in C# 2008 Express Edition. Once installed I need to change the permissions of directory C:\Program Files\Darren Link\ApplicationName so that "Users (Darren-PC\Users)" has full control. Only once this has been done can the the application create and update the configuration files. Obviosuly this is not satisfactory for the end user as they shouldn't need to make changes to directory permissions in order to get my application to run without reporting access denied errors.
Under Windows XP the application installs and is able to write the default configuration files without needing to change any of the access permissions. Under Windows 7 if I install my app to C:\ApplicationName everything works as expected. It is only a problem when installed under C:\Program Files
Is this a bug with Advanced Installer version 7.3.1 under Windows 7? If so, is a fix due soon? If I need to make changes to my Advanced Installer Project please can you give details so that I can fix my install msi for Windows 7 users?
I have excluded my configuration files from the generated msi file so that when the application is uninstalled it leaves the configuration files on the PC. The configuration files need to be retained so that when a later version of the application is installed it picks up the configuration files created by the previous version. This works fine if the user uninstalls my application via control panel before installing the new version. If however the application is left installed and a new version of the installer is ran, choosing to remove the application also removes the configuration files. Is there a reason for this inconsistency? Is there any way to ensure that the configuration files are always retained after uninstalling, no matter what the method?
Thanks and regards
Darren
FOLLOW US
Get the latest news in Application Packaging