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
- :
- InstallShield - 4 node release
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 07, 2017
10:19 AM
InstallShield - 4 node release
I have a product that uses a 4 node release number. The problem I'm running into is that on the upgrade when I want to increment only the fourth node (eg. 5.40.002.100 to 5.40.002.101), Install Shield isn't recognizing that this is an upgrade. When you look in Add/Remove Programs after the upgrade, both the old and new instances of the product are listed. Can someone help me resolve this?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 07, 2017
10:26 AM
This is not an InstallShield limitation but is a Windows Installer limitation.
Windows Installer only uses the first 3 parts of the version in upgrade scenarios, so make sure to increment your version such that one of the first 3 parts is higher than any previously shipped version. For example, if your version 1 uses Version value 1.0.1.0, then version 2 should have a Version value of 1.0.2.0 or higher (1.0.1.1 will not work here).
This has been the case for a LONG time now. Ever since Windows Installer existed I do not know of any intentions to change things at this time.
Chad
Windows Installer only uses the first 3 parts of the version in upgrade scenarios, so make sure to increment your version such that one of the first 3 parts is higher than any previously shipped version. For example, if your version 1 uses Version value 1.0.1.0, then version 2 should have a Version value of 1.0.2.0 or higher (1.0.1.1 will not work here).
This has been the case for a LONG time now. Ever since Windows Installer existed I do not know of any intentions to change things at this time.
Chad
