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: Force uninstall/install - Minor upgrades
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
‎Sep 05, 2010
12:30 PM
Force uninstall/install - Minor upgrades
I have an appication that must be uninstalled then reinstalled when I release an update to the program.
I see I can tell IS to force uninstall/install for major upgrades. Is there a way to force the uninstall and install behavior when I run minor upgrades?
Any suggestions?
Jack
I see I can tell IS to force uninstall/install for major upgrades. Is there a way to force the uninstall and install behavior when I run minor upgrades?
Any suggestions?
Jack
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2010
07:23 PM
For a minor upgrade, no, I think Windows Installer requires you to install over the existing version.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 09, 2010
06:28 AM
Robert,
Thanks for your reply.
Since I cannot force an uninstall/install I may be able to accomplish it with custom actions.
For an upgrade what would you recommend for sequence and conditions (custom actions and sequences) so that they fire 1 at the start of the upgrade and one at the end of the upgrade. What I want to do is fire something to unreg my module as the upgrade starts and then once the files are deployed fire the 2nd action call the libs to reg the modules.
Thanks,
Jack
Thanks for your reply.
Since I cannot force an uninstall/install I may be able to accomplish it with custom actions.
For an upgrade what would you recommend for sequence and conditions (custom actions and sequences) so that they fire 1 at the start of the upgrade and one at the end of the upgrade. What I want to do is fire something to unreg my module as the upgrade starts and then once the files are deployed fire the 2nd action call the libs to reg the modules.
Thanks,
Jack
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2010
06:30 PM
A minor upgrade still follows the InstallInitialize to InstallFinalize route, so the usual rules apply. The condition on the SetupResume dialog box is a good model for conditions to use on your custom actions.