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
- :
- Re: Is this a doc typo?
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
‎Jun 13, 2008
03:21 PM
Is this a doc typo?
Preventing the Current Installation from Overwriting a Future Major Version of the Same Product
In the above subject we read:
If I set the version of the current Setup for Minimum Version doesn't that disable any major upgrades from previous versions for this setup?
In the above subject we read:
To manually add support for preventing end users from being able to install the current version of your product over a future major version:
[LIST=1]Use the Upgrades view to add a major upgrade item to your project. On the Common tab, select the Products using my Upgrade Code option. Configure the settings on the Advanced tab for the major upgrade item as follows:
- In the Minimum Version setting, specify the product version that you are using for your current project.
- Leave the Maximum Version setting blank. If a value is listed for this setting, delete it.
If I set the version of the current Setup for Minimum Version doesn't that disable any major upgrades from previous versions for this setup?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 13, 2008
05:26 PM
The restriction applies only to the version in which you set up this detection and error action; later versions will use their own Upgrade table information...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 13, 2008
06:08 PM
Thanks for the reply. OK here's my case:
I have a Setup v1.0.0 that is already released. Version 1.0.0 did not have an Upgrade Item defined.
For version 1.0.5 I define a Major Upgrade item and set the upgrade version range to Minimum 1.0.5 (Current Version as instructed above) to Maximum of.
Now when I run Setup v1.0.5 over a v1.0.0 installation I get the "Cannot downgrade" error message. So I cannot even upgrade an earlier version! This is what I don't understand. Am I misreading the instructions?
Thank you
I have a Setup v1.0.0 that is already released. Version 1.0.0 did not have an Upgrade Item defined.
For version 1.0.5 I define a Major Upgrade item and set the upgrade version range to Minimum 1.0.5 (Current Version as instructed above) to Maximum of
Now when I run Setup v1.0.5 over a v1.0.0 installation I get the "Cannot downgrade" error message. So I cannot even upgrade an earlier version! This is what I don't understand. Am I misreading the instructions?
Thank you
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 13, 2008
07:37 PM
I'm assuming that the range of versions (Minimum Version - Maximum Version) identifies the range that can be upgraded by the current setup. If that's true, then setting Minimum Version as current version means any earlier versions cannot be upgraded! :confused:
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 13, 2008
10:49 PM
Right, that detects future versions, and then the steps in the documentation continue to display a message and exit if a future version is detected. A "normal" major upgrade would be a separate item that detects earlier versions and removes them.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2008
07:44 PM
Great! So I should have a second Major Upgrade item for normal upgrades. Thanks.