ozhummer
Posts: 10
Joined: Wed Jan 09, 2019 6:50 am

Automated Uninstalling in an Install

I have a situation where our application has changed several times as has the install. Problem is the current version is not associated with the old versions and when it installs the old versions are still there - this creates confusion with clients who are installing the new software.

My question is - Is there a way to uninstall another application as part of an install - almost need it as a prerequisite, so it uninstalls all old versions and a couple of unnecessary utilities before starting on the new prerequisites and new software. Can this be done in as a custom action ?

Appreciate any assistance....
belsonmarble
Posts: 65
Joined: Wed May 22, 2019 1:43 am

Re: Automated Uninstalling in an Install

In the customs action section there is an option to uninstall previous versions, you could remove the old files by going that way.
Catalin
Posts: 7845
Joined: Wed Jun 13, 2018 7:49 am

Re: Automated Uninstalling in an Install

Hello,

In order to achieve this, you can use "Upgrades" page. This page allows you to specify a list of products that will be removed from the target computer when your package will be installed.

Additionally, please have a look on our "How to upgrade an older version of the package" as well, which I think you may find useful.

@Belson,

Thank you for contributing to our forums. However, that custom action does not help in this case. The "Uninstall previous versions" custom actions is mainly used when the setups have different installation types (e.g. one has per-user type and one has per-machine type).

The custom action uses the package's "UpgradeCode" to find the older versions. The "UpgradeCode" is a GUID representing a related set of products. A set of different versions of your application will have the same "UpgradeCode". This enables newer versions of your application to search and upgrade previous versions installed on the same computer.

Since he said that the different versions are not associated, this probably means that they have a different "UpgradeCode", which makes the solution that involves the custom action invalid.

Hope this helps.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”