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: Multiple Program Instances in Add/Remove Programs
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2013
02:12 PM
Multiple Program Instances in Add/Remove Programs
Hi,
We have multiple releases for an Windows application and we're seeing multiple instances of the install in "Programs and Features" (Win 7). We'd like to have previous installs uninstalled automatically when new install is executed, but, haven't found a successful way to do this.
We followed these steps to create a setup file:
1) Increment the assembly version's release number for the app
2) Change the Product Version in installation project to match the app's assmebly version
3) Generate new GUID for Product Code
4) Build
Any help would be greatly appreciated!
We have multiple releases for an Windows application and we're seeing multiple instances of the install in "Programs and Features" (Win 7). We'd like to have previous installs uninstalled automatically when new install is executed, but, haven't found a successful way to do this.
We followed these steps to create a setup file:
1) Increment the assembly version's release number for the app
2) Change the Product Version in installation project to match the app's assmebly version
3) Generate new GUID for Product Code
4) Build
Any help would be greatly appreciated!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2013
02:48 PM
I assume from your question that you are working with a MSI project, which I have very little experience with, but have been studying lately. From what I have read a MSI Major Upgrade requires both the Product Code change and the Product Version change you indicate, but it you are setting the Product Version to the applications version, you may be running into the situation where the first three fields of the version string did not change. That is OK for the application version as all four fields are used for the file transfer version checking, but to determine if a Major Upgrade is needed MSI only checks the first three fields. (And if I am giving you useless information I apologize!)
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2013
03:06 PM
Yes, it is MSI No, it's not a useless information - I have also tried using Product version that is different from Application version with no success. I did some more research and also judging from your response, changing the major number so that it counts as an upgrade might be the way to go.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 01, 2013
03:14 PM
Changing the major release version and having different versions for Product and Application didn't work... 😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2013
10:47 AM
Do you have an entry in the Upgrade paths section?
Make sure the Max version matches your current version.
Make sure the Max version matches your current version.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)