We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

jlangland
Posts: 1
Joined: Wed Sep 12, 2012 2:37 am

4 digit Primary Version Number--for Years

Hi,

When our team decided to move to a version numbering system, YYYY.MM.WB (Week, build iteration) for weekly builds and monthly releases, we discovered that AI will only handle 3 digits in the primary version number.

Could this be increased to 4 digits?

E.g. Version # 2012.09.301= 2012, September, 3rd Week Iteration 1

Thanks for your consideration.

Jerry
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: 4 digit Primary Version Number--for Years

Hi Jerry and welcome to our forums,

Please note that we have inserted the validation over the product version field as this is a standard recommended by Microsoft. As you can see in the linked article the first two fields should not exceed 255. We recommend following the same standards to make sure that the upgrade rules applied by the OS work correctly.

However, if you still want to use your format there is one way, you need Enterprise or Architect edition. You can go into Table Editor page, in Property table and set there the value of the property "ProductVersion" manually, in the "Value" column. Please note that you need to set there the direct value, not a reference to another property. This means that every time you change the version you need to edit the project file manually.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Feature Requests”