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
- :
- Registry keys replaced during minor upgrade
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
‎Mar 12, 2009
08:55 AM
Registry keys replaced during minor upgrade
InstallScript MSI
On new install, my setup creates registry keys for some default window positions using values created in the Registry View. After setup the user can change the window positions which changes the corresponding registry keys.
On minor upgrade, the keys get reset to the original values. Is there a way to prevent this from happening?
I know I could write code to read and restore the old values, but this seems like something that should be taken care of by InstallShield. If I'm forced to do this where is the ideal place to do it AFTER the registry keys have been added?
I would think a lot of people would run into this problem. I would think the default would be to keep registry keys on a minor upgrade. Am I missing something?
On new install, my setup creates registry keys for some default window positions using values created in the Registry View. After setup the user can change the window positions which changes the corresponding registry keys.
On minor upgrade, the keys get reset to the original values. Is there a way to prevent this from happening?
I know I could write code to read and restore the old values, but this seems like something that should be taken care of by InstallShield. If I'm forced to do this where is the ideal place to do it AFTER the registry keys have been added?
I would think a lot of people would run into this problem. I would think the default would be to keep registry keys on a minor upgrade. Am I missing something?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 12, 2009
01:18 PM
If the component containing the registry entries is being reinstalled, the registry entries will be reinstalled. To prevent this issue, these entries should be in their own component (i.e., no other resources that need to be installed during upgrades should be in this component). Then, one of the registry entries should be marked as the key path of the component (right-click one of the entries and select Set Key Path). In the Components view, select the component containing the registry data and set its Never Overwrite option to Yes. This prevents Windows Installer from installing the component if the component's keypath already exists on a target machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 30, 2009
09:38 AM
Finally got around to trying that approach and it worked like a charm.
Thanks.
Thanks.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)