Problem with boilerplate upgrade configuration

[jasons2645]

How does AdvancedInstaller determine whether a currently-installed version is older or newer?

I've created an .aip file with "Automatically upgrade older product versions" and "Uninstall old version first and then install new version" and I'm getting strange behavior. AdvancedInstaller seems to think an older version (product version 0.1.BLAHBLAHBLAH) is newer than a newer version (production version 0.2.BLAHBLAHBLAH). I have to think AdvancedInstaller is looking at something other than the production version...

[jasons2645]

So after further review of the documentation, it looks like AdvInst looks at the production version, so looks like I may have uncovered a bug...

So, here's what's different between the old version's AIP and the new version's AIP. NOTHING has changed other than the below.

1) Production version changed from

0.1.201006220350
to
0.2.201006220927

2) Product code changed from

1032:{707A0E37-E99D-4947-B129-201006220350} 1040:{C7CD892B-EA2A-4113-AF91-201006220350} 1033:{EDF1B249-E9F9-4223-B1EF-201006220350} 1041:{D9AA5B87-63EB-4B66-81CF-201006220350} 1049:{6F66B355-160E-42ED-A37A-201006220350} 2057:{AFAECE82-6F05-46C4-A036-201006220350} 1042:{54DC4774-8E84-418E-9911-201006220350} 1058:{22DF9666-786E-4F88-A1CA-201006220350} 2074:{D86842C3-EFED-45C4-ABD8-201006220350} 3082:{17C70556-F5D4-4258-A9E1-201006220350} 3098:{D14165DD-67F0-492A-B662-201006220350} 1027:{B4E8A79E-AD21-48AF-A732-201006220350} 1035:{D82EECC3-E8FD-41AC-9049-201006220350} 1043:{4F36C79A-A054-4409-94D6-201006220350} 1051:{E640A53D-0882-4D20-8E03-201006220350} 1028:{9C3A0257-2C51-4672-9540-201006220350} 1036:{B01CB9BE-ED90-4832-BE34-201006220350} 1044:{3A03F3C5-7588-4E0A-8AFD-201006220350} 1052:{651E7CCF-E747-40DF-BB06-201006220350} 1060:{527FC839-D0B4-4CD8-AACB-201006220350} 2052:{0FDC2CA9-6DD0-4247-9A20-201006220350} 2068:{6B9E3F2B-4E67-4AFC-BC7B-201006220350} 1029:{2611EACB-E741-46C0-944F-201006220350} 1045:{13F3BDC3-D942-4DC0-AFB2-201006220350} 1053:{6B25A480-7E16-4A88-9BFB-201006220350} 1030:{FD3BE11F-D04E-47E8-97C2-201006220350} 1038:{C4BFD747-87A7-48DC-B673-201006220350} 1046:{3775BF4F-3AFC-4FA3-8117-201006220350} 2070:{829E4FE4-BF09-4CF5-B573-201006220350} 1031:{5EB982F0-E92D-4506-94B5-201006220350} 1055:{98CE67AC-933B-4081-B3B8-201006220350}

to

1032:{707A0E37-E99D-4947-B129-201006220927} 1040:{C7CD892B-EA2A-4113-AF91-201006220927} 1033:{EDF1B249-E9F9-4223-B1EF-201006220927} 1041:{D9AA5B87-63EB-4B66-81CF-201006220927} 1049:{6F66B355-160E-42ED-A37A-201006220927} 2057:{AFAECE82-6F05-46C4-A036-201006220927} 1042:{54DC4774-8E84-418E-9911-201006220927} 1058:{22DF9666-786E-4F88-A1CA-201006220927} 2074:{D86842C3-EFED-45C4-ABD8-201006220927} 3082:{17C70556-F5D4-4258-A9E1-201006220927} 3098:{D14165DD-67F0-492A-B662-201006220927} 1027:{B4E8A79E-AD21-48AF-A732-201006220927} 1035:{D82EECC3-E8FD-41AC-9049-201006220927} 1043:{4F36C79A-A054-4409-94D6-201006220927} 1051:{E640A53D-0882-4D20-8E03-201006220927} 1028:{9C3A0257-2C51-4672-9540-201006220927} 1036:{B01CB9BE-ED90-4832-BE34-201006220927} 1044:{3A03F3C5-7588-4E0A-8AFD-201006220927} 1052:{651E7CCF-E747-40DF-BB06-201006220927} 1060:{527FC839-D0B4-4CD8-AACB-201006220927} 2052:{0FDC2CA9-6DD0-4247-9A20-201006220927} 2068:{6B9E3F2B-4E67-4AFC-BC7B-201006220927} 1029:{2611EACB-E741-46C0-944F-201006220927} 1045:{13F3BDC3-D942-4DC0-AFB2-201006220927} 1053:{6B25A480-7E16-4A88-9BFB-201006220927} 1030:{FD3BE11F-D04E-47E8-97C2-201006220927} 1038:{C4BFD747-87A7-48DC-B673-201006220927} 1046:{3775BF4F-3AFC-4FA3-8117-201006220927} 2070:{829E4FE4-BF09-4CF5-B573-201006220927} 1031:{5EB982F0-E92D-4506-94B5-201006220927} 1055:{98CE67AC-933B-4081-B3B8-201006220927}

Any ideas as to why the newer version is recognized as the older one?

[GabrielBarbu]

Hello,

The third field in your version is too large. The version number can have a range from 0.0.1 to 255.255.65535. Please correct your version numbering then try again.

Best regards,
Gabriel

[jasons2645]

Where does this limitation stem from? Is there a way to remove this limitation? (the version number, as verbose as it is, contains quite useful information and we'd very much prefer not to truncate it)

[jasons2645]

Also, our version number format has changed once more to be of the form 0.2.1.201006220927. Can we have this fourth place and if so, what is the maximum we can have for the last field with the current limitation?

Note that lack of support of a fourth place we can work around - not being able to have a long last number is a much larger issue. Thanks!

[GabrielBarbu]

Hello Jason,

The limitation is imposed by Microsoft.
You can check this page discussing the ProductVersion Property for more details.
You can include a fourth field which will be ignored by Windows Installer. You can use that for informational purposes.

Best regards,
Gabriel

[jasons2645]

Thanks!