InstallShield 2016 » Upgrades View » Minor Upgrade Item
Project • This information applies to the following project types:
• | Basic MSI |
• | InstallScript MSI |
Minor and small upgrades are fundamentally the same except with minor upgrades, the product version changes.
You need to apply a small/minor upgrade any time you are upgrading a setup that has the same product code as the latest version of your setup. You are not required to change the product code of a setup unless you delete a component from a feature or you delete a feature from a setup.
Note • If you move a component from one feature to another, you are essentially deleting that component from the first feature and therefore must change the product code.
For upgrade scenarios in which the setup’s product code has changed, you must apply a major upgrade.
This tab exposes the following settings:
Option |
Description |
Setup to Upgrade |
The functionality required to install a minor upgrade is in Setup.exe, which you must include in order for a minor upgrade to work properly. The setup specified at build time will also be used to perform upgrade validation. The build will also verify that the referenced setup can be updated using a minor upgrade. Note that the build will warn you if you do not include setup.exe when you build your release. |
Release Flags |
Specify release flags to include and exclude features depending on the type of release. |
See Also
Run-Time Behavior for Minor Upgrades
Determining the Best Upgrade Solution
Packaging Options for Upgrades
Preventing the Current Installation from Overwriting a Future Major Version of the Same Product
InstallShield 2016 Help LibraryAugust 2016 |
Copyright Information | Flexera Software |