Same build "version" doesnt detect

[FergusMurray]

Got an issue with our installers

At the moment we are "rebuilding" the same version number (5.1.3) for testing, but when we come to install on the same test pc's that had the old version of (5.1.3) advanced installer isnt aware of the install being there at all and installs a fresh copy of the application

Can this be fixed?

[Bogdan]

Normally the message "Another version ..." should appear when you try to install the package on a machine were the same version of it was installed.

If this message does not appear and the product version is the same you need to check the product code of the new package was changed, maybe using an automated script or something else like that?

Regards,
Bogdan

[FergusMurray]

We use an .aic to pass to the build scripts, would this changed the product code?
(using v9.0 atm, even tho directory says 8.5...)
"%programfiles32%\Caphyon\Advanced Installer 8.5\bin\x86\advancedinstaller.com" /execute Installer\AiDPS.aip SetBuild.aic

Where SetBuild.aic is:
;aic
SetVersion 5.1.3
Save
Build

[FergusMurray]

Ran a test and the PRODUCT CODE does change when that command is issued, so the 2 (internal) versions of 5.1.3 will have different product codes, but should it not still be aware of it since the UPGRADE CODE is the same?

[mihai.petcu]

If the Product Code has changed, this is the reason you are getting this behavior. Usually, the product code should automatically change when you change the product version, not when you modify the project.
Another automatic scenario when the product code is different for same versions is when the packages have different languages. Since you didn't mention this, I guess this is not the case.

If the “Automatically upgrade older versions...” option is selected in the Upgrades page, on install Windows Installer will search for and uninstall all the products with the same Upgrade Code and older Versions.

All the best,
Mihai

[FergusMurray]

Hi Mihai,

The option is set to upgrade older versions.

Our installers are in a version control (SVN) system, during the install we set the version number at build time, and this "changes" the aip file, and marks it as modified within the version control system, so after the build we revert the changes (as part of our automated scripts), so its likely that this causes the product code to change for every build (even on the same version)

To me it seems a gap in advanced installer that you dont detect the same version number with a different product code, and you should really be covering these holes.
if you have a greater version number you get a message
if you have a lesser version number you get a message
if you have the same version number (but different product code due to using AIC commands during a "rebuild") then, no message and it installs a duplicate copy.

[Daniel]

Hi,

To me it seems a gap in advanced installer that you dont detect the same version number with a different product code, and you should really be covering these holes.

Please keep in mind that this is a normal behavior of side-by-side installation. In order to avoid this you should not generate a new product code when you are setting the version number from command line ( use -noprodcode command line option).

Regards,
Daniel