New builds of project not detected as upgrades

[peterk]

So we have been using AI for awhile on our older project and we allow side-by-side installations with environment variables allowing for customization.

We have a new project starting from scratch using AI 21.7.1 and initial installation goes just fine. Version 1.0.0 installs and is doing great. When we create a new version (building in TeamCity using the AI plugin) we build the .aip file. Now we have a step prior to building the AI project that does some API manipulation of the .aip file including running the /SetVersion 1.0.1 command.
So when we now install the update (version 1.0.1), Windows 10 doesn't seem to understand that its an upgrade but installs 1.0.1 as a new product. So now I have product FOO in Windows registered as 1.0.0 and 1.0.1 next to each other in the Windows installed programs list. Are we doing something wrong here by manipulating the .aip file before using the plugin? I don't think it would make a difference as the example using the TC plugin actually has SetVersion as an option.

Under the Upgrades menu I have:
Automatically upgrade older product versions
Use original installation path when upgrading
Uninstall old version first and then install the new version

[Catalin]

Hello Peter,

The program being installed side by side would usually point out to your two installers having different UpgradeCodes - this is usually the case where the OS thinks they are different apps.

Could you please check that and let me know if that's the case?

Note: you can get the UpgradeCode of your installed application through PowerShell, for example, as displayed here:

Find UpgradeCode of installed MSI file

Best regards,
Catalin

[peterk]

I ran the script found on the link and It indeed shows that we have two product codes sharing one upgrade code for the product installed

Code: Select all

ProductCode                            UpgradeCode                            Name
-----------                            -----------                            ----
{A6BABACE-567C-4A6E-9786-87C4A275505E} {09D9A38A-66D7-4037-A43C-20CEF2CCDEF0} SCA Agent
{C0C45388-BFC2-45A4-921F-3C2DB744DBB4} {09D9A38A-66D7-4037-A43C-20CEF2CCDEF0} SCA Agent

[Catalin]

Hello Peter,

This is quite strange.

If possible, could you please forward me the following resources:

- a download link for v1

- a download link for v2

- the AIP file for v1

- the AIP file for v2

by email at support at advancedinstaller dot com so I can test and investigate this on our end?

Best regards,
Catalin

[Catalin]

Hello,

For everyone reading this post, this behavior was caused by the wrong usage of the "Version" field.

As per Microsoft documentaiton, the ProductVersion property should be of this form: 255.255.65535, so:

- first field max value of 255

- second field max value of 255

- third field max value of 65535

ProductVersion Property

Best regards,
Catalin