Invalid IS 2010 action Version Properties

FinalBuilder Bugs
1

FB: Version 6.3.0.1712

InstallShield 2010 Action | Properties | Override Parameters

Override Parameters tab on InstallShield 2010 Project action allows for setting 4 version settings from a property set, however, Microsoft Intaller only supports 3 version numbers (even though 4 can be specified, MSI won't use more than 3) 
Specified as: (My Example values: Maj: 4 Min: 5 Rel/Rev: 0 Build 730)

Use Major, Minor, Build & Release/Revision Version Numbers or
Use Major, Minor, Release/Revion & Build Version Numbers (expected: 4.5.0.730) -- (received 4.5.730.0)

(This seems to indicate only 3 will be used, but in fact 4 are placed in the install for "ProductVersion")

Previous versions of InstallShield actions (2008, 2009) limited the property set to 3 numbers.
Specified as:

Use Major, Minor & Build Version Numbers or
Use Major, Minor & Release/Revision Version Numbers

So, when updating the version on our product with IS2009 action, version numbers (in add/remove programs) would show as 4.5.730 now show as 4.5.730.0 (with IS2010 action) but file versions show as 4.5.0.730 - we can't use the first option to use 4.5.0.730 because MSI will only "see' 4.5.0 for the version - which will cause upgrade issues.

Also, I chose to use the format specified by "Use Major, Minor, Release/Revion & Build Version Numbers" - but, as shown above, the BUILD number is 730 - which is being placed before Release/Revision (of 0) in the version number - so, these appear to also be backwards as far as formatting according to the user interface.

Issue #1: 4 build numbers instead of 3 (which is max supported by MSI)
Issue #2: Incorrect formatting of the numbers between UI and actual product update for version number

2

Hi Kent

IS 2010 allows 4 values, however MSI ignores the 4th value. The issue #2 you found is a bug, I have changed the behavior to match the UI :

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1755.exe

3

So, are you saying that issue #1 is not a bug?

Maybe the documentation can clairify things a bit?

Maybe there is a workaround, or should this be a feature? - e.g. Another radio button to only use 3 version numbers (and leave the radio buttons for 4 version numbers if others want to try and use that?)

4

Hi Kent

The ability to specify a fourth number was added at the request of an FB/IS2010 user, after he quoted the same text from the help file.