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
- :
- Re: Upgrade issue....Urgent!!!!
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
‎Jun 22, 2009
07:00 AM
Upgrade issue....Urgent!!!!
Hi All,
I have a product with ProductName XXX and Version 1.0.0.0 Now I have to upgrade it to Version 1.0.0.1, each time I build I change the ProductName also, to reflect the version in the name.
When I try to install the newer version I am getting the following error which I have attached.
The current installer is searching for the previous installed version .msi file in the current source location.
Is there any workaround for this issue.
I have the previous version of the product already released to the customer, which has its version in ProductName.
So I cannot keep the same product name for my new releases.
Any help is appreciated.
Thanks ....
Anitha
I have a product with ProductName XXX and Version 1.0.0.0 Now I have to upgrade it to Version 1.0.0.1, each time I build I change the ProductName also, to reflect the version in the name.
When I try to install the newer version I am getting the following error which I have attached.
The current installer is searching for the previous installed version .msi file in the current source location.
Is there any workaround for this issue.
I have the previous version of the product already released to the customer, which has its version in ProductName.
So I cannot keep the same product name for my new releases.
Any help is appreciated.
Thanks ....
Anitha
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 22, 2009
11:36 AM
Windows Installer does not allow the name of an MSI package to change for small updates or minor upgrades (a major upgrade is required). Since InstallShield builds the MSI package based on the current product name in a project, the MSI filename will change if the product name has changed. To resolve this, do not change the product name, or specify the original MSI filename in the "MSI Package File Name" field in the product configuration for the release you are building (in the Releases view).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 22, 2009
01:34 PM
Hi,
If you are using IS2K9 (or even IS 12) you will be having options for specifying previous releases in patch desgin panel. The final MSP (patch) of this release will be a hash image of your previous and latest releases which will be error prone and provide THE BEST OUTPUT. If you are changing your package name, then the upgrade will be a MAJOR UPGRADE.
Also ensure that before creating patch, ensure that all your previous products got uninstalled, delete traces from registry (like shared dlls, UNINSTALL,APPPATH) and clearn TEMP (this is very must).
Please have a look of the attached screenshot with respect to upgrades.
If you are using IS2K9 (or even IS 12) you will be having options for specifying previous releases in patch desgin panel. The final MSP (patch) of this release will be a hash image of your previous and latest releases which will be error prone and provide THE BEST OUTPUT. If you are changing your package name, then the upgrade will be a MAJOR UPGRADE.
Also ensure that before creating patch, ensure that all your previous products got uninstalled, delete traces from registry (like shared dlls, UNINSTALL,APPPATH) and clearn TEMP (this is very must).
Please have a look of the attached screenshot with respect to upgrades.