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
- :
- Build versions
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 10, 2010
05:26 PM
Build versions
Our company has been using one digit major releases and one digit minor releases and 4 digit build numbers....example:
2.1.0101, 2.2.0101, .....2.9.0101
And now our product management department wants the next minor version to be:
2.10.0101
Will there be any problems with this? Will IS recogize the 10 being greater than 9 if it were treated numerically or does it look at 10 as alpha numeric and it would treat 2.10 the same as 2.1?
Would it be better to just use 3.0 instead?
2.1.0101, 2.2.0101, .....2.9.0101
And now our product management department wants the next minor version to be:
2.10.0101
Will there be any problems with this? Will IS recogize the 10 being greater than 9 if it were treated numerically or does it look at 10 as alpha numeric and it would treat 2.10 the same as 2.1?
Would it be better to just use 3.0 instead?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 17, 2010
12:11 PM
Assuming you're talking about an MSI project, a quick test shows setup.exe correctly detecting 2.9.0101 is earlier than 2.10.0101 for a minor upgrade, applying the upgrade from 2.9 to 2.10 and refusing to install 2.9 over 2.10...