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
- :
- UNINSTALL Required first?
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
‎Nov 20, 2012
01:57 PM
UNINSTALL Required first?
Whenever I build an installer with a new version number, when the user tries to install the new one it stops and says user must UNinstall the current version. How do I make it automatically overwrite the current version?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 20, 2012
09:02 PM
The help topic "Adding an Upgrade Item" might get you started.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 04, 2012
04:53 AM
We also came across this. The reason is that the Product Code is the same between your builds (even you change the version number). Remember that the Upgrade Code must always be the same!
I'm sure that, if you change the Product Code it will upgrade correctly. If you release a new version it is always a good idea to change the Product Code, but for intermediate builds this could be a little cumbersome.
Therefore, play with the Upgrade Path. And set the Upgrade Path to include the version you are installing. This worked for us when creating new ISX projects, we however had problems with older upgrades projects.
Alternatively you can make an automated build tool that changes the version number and product code before building the project. As hint, you can use the "WindowsInstaller.Installer" object and treat the ISX project file as a database looking for e.g. the "ProductCode" property.
-cpede
I'm sure that, if you change the Product Code it will upgrade correctly. If you release a new version it is always a good idea to change the Product Code, but for intermediate builds this could be a little cumbersome.
Therefore, play with the Upgrade Path. And set the Upgrade Path to include the version you are installing. This worked for us when creating new ISX projects, we however had problems with older upgrades projects.
Alternatively you can make an automated build tool that changes the version number and product code before building the project. As hint, you can use the "WindowsInstaller.Installer" object and treat the ISX project file as a database looking for e.g. the "ProductCode" property.
-cpede
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)