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 and Patch
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
‎Aug 25, 2008
05:00 PM
Upgrade and Patch
I have a released msi and I want to create a patch for current users. I also need to create a new release that new users will download. I was able to make the patch and it updated the version number to the current release. However, I ran the new complete msi and it allowed the install and created a second entry in add/remove programs. Is it possible to create a patch that the full version would recognize and either replace or not install?
Thanks in advance
Owen
Thanks in advance
Owen
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 03, 2008
10:28 AM
There have been over 7000 views but no one has any ideas?
I can't be the only one who would like to create a patch and have the patch be overwritten be the full install when both of them result in the same version.
I can't be the only one who would like to create a patch and have the patch be overwritten be the full install when both of them result in the same version.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 04, 2008
09:17 PM
Since the new MSI was installed next to your updated former package, it sounds as though you have 2 different projects for them.
I would suggest targeting the former package in the current package as seen in the Upgrade Paths view. This would allow the installation process of the newest package to uninstall instances of the former package.
See the help library topic, "Upgrade Paths View".
I would suggest targeting the former package in the current package as seen in the Upgrade Paths view. This would allow the installation process of the newest package to uninstall instances of the former package.
See the help library topic, "Upgrade Paths View".
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)