Multiple product versions in Control Panel

[d79ima]

Hello,

Our product is built using continuous integration nightly and each build creates an installer with an incremented product version.

The problem is that every time the customer runs the installer they get a new entry for our product in the Control Panel.
Is it possible to overwrite existing Control Panel entry on each successive product install?

Thanks,
Dmitry

[Dan]

Hello,

I'm not sure why you encountered this behavior.

This may happen if you generate each time a new “Upgrade Code”.
Different versions of your application should have the same UpgradeCode in order to allow newer version of your application to search and upgrade previous versions installed on the same machine and not create a new entry in the “Add/Remove Programs” list from Control Panel.

Can you also make sure you don't have the “Allow side by side installs of different product versions” option enabled from the “Upgrades” page.

Also you can take a look on Duplicate Control Panel entries thread which debates a similar issue.

If the behavior still persist can you please send us two consecutive versions of you application to support at advancedinstaller dot com so we can investigate the behavior?

Best regards,
Dan

[d79ima]

Hi,

The Upgrade Code does not change between consecutive builds of the installer.
“Allow side by side installs of different product versions” is not enabled from the "Upgrades" page.

"Duplicate Control Panel" entries thread points to "Override Windows Installer programs list entry" being checked, which it is not for me.

Our installers are quire large(100+ MB), too large to e-mail. Can I ftp it to you guys? If so, can you please specify your FTP server login info.

Thanks,
Dmitry

[d79ima]

Hi,

I still have not received any reply. Is there a good way to FTP my large installer applications to you so that you can explain the behavior I am seeing???

Thanks,
Dmitry

[Daniel]

Hello Dmitry,

First of all I apologize for my delayed response. We are quite busy at the moment.

We cannot post the ftp details on the forum due to security matters. However, can you please first send us both .AIPs (only project files of your upgrade and upgraded package reproducing this issue) to support at advancedinstaller dot com so we can investigate them?

All the best,
Daniel

[d79ima]

Hi,

I just sent two copies of my installer .aip project files to the address specified.

Please let me know whether you can reproduce the problem or not.

Thanks,
Dmitry

[Daniel]

Hello Dmitry,

This happens because in both of your installation packages (the upgraded and upgrade one) the first three product version fields are identical. Please keep in mind that Windows Installer ignores the fourth field of the product version. So, if your first three product version fields are identical, then the new version of your application will not upgrade the previous one. Please take a look on "ProductVersion property" article and set your product version accordingly in order to achieve what you want.

If you have any questions let us know.

All the best,
Daniel

[d79ima]

Hi,

Thanks for the reply.
We have been keeping this 4 part product version convention in our product for the last 7 years and I would hate to change it now.
Is there any workaround you can suggest that would achieve the same desired goal without having to change the build(3rd part) of Product Version?

Thanks,
Dmitry

[Daniel]

Hello Dmitry,

As a workaround you can try to use our "Uninstall previous versions" predefined custom action.

Let us know if this helped.

All the best,
Daniel

[d79ima]

I tried this custom uninstall action, but it didn't seem to work.
This is the line that was added to my .aip file:

<ROW Action="UninstallPreviousVersions" Type="1" Source="aicustact.dll" Target="UninstallPreviousVersions" WithoutSeq="true" Options="3"/>

Is this correct, or do I need to do something else to get it to work?

[Dan]

Hello Dmitry,

Can you please add the "Uninstall previous versions" custom action as a custom action with sequence, scheduled before "Wizard Dialogs Stage" -> "Paths Resolution" action group, and see if the behavior still persist?

Best regards,
Dan

[d79ima]

Thanks Daniel,

That seems to work!