Why adding an extra previous setup breaks upgrade path in InstallShield?

1
votes

I'm creating a patch for my product. This is the third patch for the base version. My upgrade paths are as follow:

  • 1.0 -->1.0.3
  • 1.0.1 -->1.0.3
  • 1.0.2 -->1.0.3

What I did was to create a new patch in Patch View and set 1.0.3 as the latest version and 1.0, 1.0.1 and 1.0.2 as the previous versions. (I followed the same approach when created the patches 1.0.1 and 1.0.2)

The problem I have is that the upgrade path from 1.0 to 1.0.3 is NOT working, but only if I add 1.0.2 to the previous versions list. If I remove 1.0.2 from the previous versions, the 1.0-->1.0.3 upgrade path works perfectly.

Does anybody know what could be wrong in this scenario?

Note: I have seen this issue in both InstallShield 12 and InstallShield 2011.

Note 2: Could someone please tag this as InstallShield-2011 and InstallShield-12, the tags don't exist and I cannot create them because don't have enough points. Thanks.

Any advice will be appreciated.

Thanks,

Juan C. Becerra

1
windows-installerinstallshieldpatch

1 Answers

0
votes

It sounds like some component rules may be broken in the 1.0.2 installer. To find out where the problem may lie, I'd recommend running the Upgrade Validation Wizard, which you can get to from the menu by clicking Build | Validate | Upgrade Validation Wizard...

Here, you can specify your most current setup, and specify the paths to the previous ones, and then it will check to see if there could be any problems that may result in a failed upgrade scenario.

Best of luck,

Bryan