This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Thanks a lot!
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2009
03:07 AM
InstallLocation registry entry empty after minor upgrade
Hi,
I am working on a Basic MSI project using Installshield 2008.
I have noticed that the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}\InstallLocation] registry entry is ok after the first installation, but it is emptied by a minor upgrade.
Let me describe the procedure:
[LIST=1]
Install version 1.0 of my product. The target folder is C:\Program Files\MyCompanyName\MyProgramName\.
The above registry entry is correctly set to "C:\Program Files\MyCompanyName\MyProgramName\"
Perform a minor upgrade using the version 1.1 of the MSI package.
The above registry entry is still present but it is empty.
Now if I directly install version 1.1 to the same target folder, the registry entry is set correctly.
Is that behaviour normal?
Can this empty registry entry lead to some problems later? It does not seem to cause any problem when deinstalling or using the program.
Have I forgotten to set any property during the first installation or during the minor upgrade?
Regards
I am working on a Basic MSI project using Installshield 2008.
I have noticed that the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductCode}\InstallLocation] registry entry is ok after the first installation, but it is emptied by a minor upgrade.
Let me describe the procedure:
[LIST=1]
The above registry entry is correctly set to "C:\Program Files\MyCompanyName\MyProgramName\"
The above registry entry is still present but it is empty.
Now if I directly install version 1.1 to the same target folder, the registry entry is set correctly.
Is that behaviour normal?
Can this empty registry entry lead to some problems later? It does not seem to cause any problem when deinstalling or using the program.
Have I forgotten to set any property during the first installation or during the minor upgrade?
Regards
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2009
06:05 PM
This registry entry is set from the value of the ARPINSTALLLOCATION property. This property is set by a custom action named SetARPINSTALLLOCATION. By default, this custom action has a condition of Not Installed, which becomes false after a first time install.
You can remove the condition from the SetARPINSTALLLOCATION custom action or leave it if the InstallLocation registry value does not need to be queried.
InstallShield 2009 removes the Not Installed condition from this custom action on new projects.
You can remove the condition from the SetARPINSTALLLOCATION custom action or leave it if the InstallLocation registry value does not need to be queried.
InstallShield 2009 removes the Not Installed condition from this custom action on new projects.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 20, 2009
01:42 AM
hi Josh,
Thanks a lot for your reply.
Good to know that it has been fixed in Installshield 2009.
Regards
Thanks a lot for your reply.
Good to know that it has been fixed in Installshield 2009.
Regards
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 23, 2011
08:29 AM
For what it's worth. The Not Installed condition is still used to control the action of SetARPINSTALLLOCATION in IS 2010.
Richard
Richard
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 23, 2011
12:19 PM
The SetARPINSTALLLOCATION action condition was removed for new Basic MSI and InstallScript MSI projects starting with IS 2009. The condition is not removed on projects that are migrated from previous versions of InstallShield to 2009 or newer.