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
- :
- ISPreventDowngrade - Editing the Min-version at build time
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
Jul 21, 2014
02:17 PM
ISPreventDowngrade - Editing the Min-version at build time
Our build numbers change with every build (XX.XX.YYDAYOFYEAR.DailyReleaseNumber-Incremented). We build using TFS and issue an InstallShield command line to build the installer through a post-build script (powershell). We use Basic MSI for our installer project.
I'm currently manually updating the Upgrade Item for ISPreventDowngrade so that the minimum version is in the ball-park of what the version will be when we release. Since we may not know exactly what the version will be until build time, is there a way to set the Minimum Version in the IsPreventDowngrade upgrade item to be the new build number instead of manually editing it every time we run a build (or predicting a number that will be used in the future).
I'm currently manually updating the Upgrade Item for ISPreventDowngrade so that the minimum version is in the ball-park of what the version will be when we release. Since we may not know exactly what the version will be until build time, is there a way to set the Minimum Version in the IsPreventDowngrade upgrade item to be the new build number instead of manually editing it every time we run a build (or predicting a number that will be used in the future).
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 22, 2014
01:26 AM
The Minimum Version only needs to be higher than any already-released versions that you don't want to trigger an upgrade. It is not necessary to change it with every build. No matter what your build number ends up at when you release, you should have a branch of your project for the major and minor version of that release that has a static setting for Minimum Version. Adding the date and individual build numbers shouldn't change anything regarding the major/minor version numbers you want covered by your upgrade item.
If you are dead set on editing this every time, you could always save the project as xml instead of binary and then edit the project file in your build automation scripts.
If you are dead set on editing this every time, you could always save the project as xml instead of binary and then edit the project file in your build automation scripts.