cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Pilgrim

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?
Labels (1)
0 Kudos
1 Reply
Highlighted
Occasional contributor

Re: InstallShield - 4 node release

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
0 Kudos