nicw
Posts: 11
Joined: Tue Mar 20, 2007 3:00 am

Three digit version numbers useless

Please consider supporting 4 digit version numbers as Windows exe's support and Visual Studio Supports. Three digit as you use now are useless, with bi-daily or weekly builds we are ramping through version numbers at an enormous rate. We really need to start using 1.0.0.1 instead of 1.0.1
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Re: Three digit version numbers useless

Hi,

Note that the three digit limitation applies only to the value of the ProductVersion Property, not to the executable files in your package (which can have four fields in their versions). As it is mentioned in the SDK, the fourth field can be included, but it is ignored (which means that "1.2.3.4" and "1.2.3.7" will represent the same ProductVersion value).

This is a Windows Installer limitation and it is not related to Advanced Installer.

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/
EdT
Posts: 1
Joined: Fri Feb 06, 2009 5:13 pm

Re: Three digit version numbers useless

Windows Installer version number fields have the following limits, set by Microsoft.
First Field - 0-255
Second Field - 0-255
Third Field - 0-65535
Fourth Field 0-65535 (Fourth field not checked in Product Version property but available in file properties)

You must certainly be creating very unstable software if you are running up against the 65535 limit on the third field, let alone the combined limit of another 256 x256 from the first two fields. Even Windows 7 beta is still under well under 10000 for the build number....;)

Return to “Feature Requests”