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
- :
- Minor Upgrade Question
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
Aug 02, 2010
11:29 AM
Minor Upgrade Question
I have a question regarding Minor Upgrades in Basic MSI projects (using InstallShield Professional). Consider this scenario:
Original Installation v1.00
Minor Upgrade v1.01 (references original installation when creating minor upgrade)
Minor Upgrade v1.02
My question is, should Minor Upgrade v1.02 reference Minor Upgrade v1.01 when defining the minor upgrade, or should it reference back to Original Installation v1.00? Or does it matter?
Thanks.
Original Installation v1.00
Minor Upgrade v1.01 (references original installation when creating minor upgrade)
Minor Upgrade v1.02
My question is, should Minor Upgrade v1.02 reference Minor Upgrade v1.01 when defining the minor upgrade, or should it reference back to Original Installation v1.00? Or does it matter?
Thanks.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 04, 2010
01:44 PM
Minor upgrades are related by the fact that the product code for the packages does not change across versions (as opposed to a major upgrade which does change the product code). Therefore, any MSI packages sharing a product code but with incremented versions and different package codes are defined as minor upgrades. As such, there is nothing to reference when creating minor upgrades (if you are referring to minor upgrade items in the Upgrades view, these are not required to author minor upgrades, they only allow for automatic upgrade validation when building). If you are using dynamic file links and the previous package release setting, each upgrade package release will point to the previous built version.
Note that if you are creating minor upgrade patches, and you want to be able to target all previous package versions, all these previous packages do need to be added to your patch configuration when creating the patch.
Note that if you are creating minor upgrade patches, and you want to be able to target all previous package versions, all these previous packages do need to be added to your patch configuration when creating the patch.
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)