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: Upgrades Not Quite Right
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
‎Feb 15, 2010
10:22 AM
Upgrades Not Quite Right
For several years we have used IS 12 to create the installers for our product, and I am in the process of rewriting our installer with IS 2010. This is an installscript project.
With our old installer, the upgrade procedure was to uninstall the old version (leaving some files behind) and then install the newer version on top of it. One of the main things we're trying to do with this rewrite is to start using the built-in upgrade features of InstallShield.
Here is my current setup:
- Our builds are created by an Ant script. The Ant script builds all the files for our product, then executes IsCmdBld.exe to create the installation with those files.
- The Ant script creates an environment variable containing the product version for this particular build in the form "1.2.3".
- The InstallShield project has General Info > Product Version set to an environment path variable that grabs this value.
This seems to work for upgrading...mostly. I manually changed the version in the IS project to get two installers, each with identical files, but different version numbers. Call them v1 and v2.
I install v1, then run the v2 installer and it performs an upgrade, as expected. But then when I go into Add/Remove Programs, the version number listed is still v1. If I try running the v2 installer again, it still offers to upgrade, even though it should already be installed. I would expect to get the maintenance options.
The IS documentation hasn't been very helpful. Can anyone tell me where I'm going wrong here?
With our old installer, the upgrade procedure was to uninstall the old version (leaving some files behind) and then install the newer version on top of it. One of the main things we're trying to do with this rewrite is to start using the built-in upgrade features of InstallShield.
Here is my current setup:
- Our builds are created by an Ant script. The Ant script builds all the files for our product, then executes IsCmdBld.exe to create the installation with those files.
- The Ant script creates an environment variable containing the product version for this particular build in the form "1.2.3".
- The InstallShield project has General Info > Product Version set to an environment path variable that grabs this value.
This seems to work for upgrading...mostly. I manually changed the version in the IS project to get two installers, each with identical files, but different version numbers. Call them v1 and v2.
I install v1, then run the v2 installer and it performs an upgrade, as expected. But then when I go into Add/Remove Programs, the version number listed is still v1. If I try running the v2 installer again, it still offers to upgrade, even though it should already be installed. I would expect to get the maintenance options.
The IS documentation hasn't been very helpful. Can anyone tell me where I'm going wrong here?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2010
03:59 AM
please go through these thread. Hope it might solve your problem.
http://community.flexerasoftware.com/showthread.php?t=185545
http://community.flexerasoftware.com/showthread.php?t=185545
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 16, 2010
09:17 AM
Thank you for the reply, but it doesn't look like the information in that thread applies to our project. We are using pure installscript, not installscript msi. Also, we do not end up with 2 entries in Add/Remove programs. There is only one entry, but it displays the v1 information even after an upgrade to v2.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2010
01:02 AM
script will run OnupdateUIBefore(), instead of MaintUI() if its upgrade. Checks for version for doing this.
For upgrade u need version change in any x, in x.x.x.y version
For upgrade u need version change in any x, in x.x.x.y version
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2010
09:13 AM
OnUpdateUIBefore is run when trying to upgrade, so that makes it seem like it's picking up the correct version number and doing what it's supposed to. It's only the version # in add/remove programs that doesn't get updated. I have customized OnUpdateUIBefore and OnUpdateUIAfter. Do I have to manually change the add/remove programs entry in one of these functions?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 18, 2010
09:25 AM
I believe that there is string value you have to modify.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)