By default the product version is as following in the .aip file
<ROW Property="ProductVersion" Value="1.0.0" Type="32"/>
I need to include build Id (i.e. BuildIDx) in the product version. If I include in the product details through GUI, it gave the error "The specified version is not supported. A valid version has been generated and set"
I manually changed the .aip file in text editor to following and compiled on command prompt and it worked and generated the required .msi file.
<ROW Property="ProductVersion" Value="1.0.0-BuildID1" Type="32"/>
I build using the same .aip file again with new build iD (i.e. BuildID2) after making following change (also manually changed the "ProductCode" to avoid "Another version of this product is already installed" problem.)
<ROW Property="ProductVersion" Value="1.0.0-BuildID2" Type="32"/>
Then required .msi is generated and perfectly update the existing installation (BuildID1) on the target machine with (BuildID2).
The next and actual problem is that, now I can see two installations in the add/remove programs i.e. MyProgram version 1.0.0-BuildID1 and MyProgram version 1.0.0-BuildID2. Whereas there is actually only one installation (1.0.0-BuildID2) as there is only one .exe (BuildID2) in the installation directory. If I uninstall MyProgram version 1.0.0-BuildID1 from add/remove programs then it does nothing and actual un-install is performed when I un-install version 1.0.0-BuildID2.
Questions:
1. Why we cannot include build ID in the product version, whereas it is common practice.
2. Why I am having two programs shown in add/remove programs.
FOLLOW US
Get the latest news in Application Packaging