- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- How to always force a major upgrade?
- 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
How to always force a major upgrade?
In our CI/CD we update the build number (4th digit) every build and don't always update the other three digits. If you install a version with a different build number then it adds a second entry for the application to Add/Remove Programs. Is it possible to force a Major Upgrade when only the build number changes?
1.0.0.300 -> 1.0.0.301
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
There are few things going on here - firstly Windows Installer does not read the 4th part of the version number. So the change that you are making will not cause any change to the Windows Installer behaviour:
https://docs.microsoft.com/en-us/windows/win32/msi/productversion
Secondly - you can only force a Major Upgrade by changing the ProductCode in your project as well. This allows the Windows Installer to understand that you want the install to behave like a Major Upgrade.
We have step-by-step instructions on how to create a Major Upgrade here:
https://community.flexera.com/t5/InstallShield-Knowledge-Base/Create-a-Major-Upgrade/ta-p/3879
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Both the Product and Package codes need to change in order to make a major upgrade. Do not change the Upgrade code.