This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Upgrade Paths
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 07, 2008
11:01 PM
Upgrade Paths
Hi,
I am having trouble with my installation picking up previous versions and upgrading them.
I have added an upgrade path, but cannot seem to get it to find the previous version and upgrade it, i constantly get the message upon installation of the upgrade:
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
I have even set the upgrade path to not include min/max version and exlude the language identifier and yes to ignore remove failure. I have also made sure the the Upgrade Code of the upgrade path matches the upgrade code of the install. The upgrade path is in the same project as the main install, could that be the problem ? I'd rather not have to make a new project for every upgrade though.
The only way i have found around this problem, is to change the product code for every build, which then creates multiple entries in the end users add/remove programs
I am having trouble with my installation picking up previous versions and upgrading them.
I have added an upgrade path, but cannot seem to get it to find the previous version and upgrade it, i constantly get the message upon installation of the upgrade:
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
I have even set the upgrade path to not include min/max version and exlude the language identifier and yes to ignore remove failure. I have also made sure the the Upgrade Code of the upgrade path matches the upgrade code of the install. The upgrade path is in the same project as the main install, could that be the problem ? I'd rather not have to make a new project for every upgrade though.
The only way i have found around this problem, is to change the product code for every build, which then creates multiple entries in the end users add/remove programs
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 09, 2008
01:51 PM
Are you changing the Package Code and Product Version for every build?
(If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)