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: Merge module best practices - uninstall
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 01, 2008
08:49 AM
Merge module best practices - uninstall
I was wondering if anyone had any insight to pass on regarding best practices for merge modules. I realize that individual key files of merge modules (and all installers) have a registry entry to keep track of reference counting to know if other applications still need it. But what about files such as sql databases which are created dynamically via sql scripts and not traditional copy of files?
Scenario
Merge module X is installed with multiple product installers (ie. Product A, Product B, etc.). The merge module includes a sql database. When / how is it best to uninstall the sql database? I am assuming that creating a custom action with condition detecting if is an uninstall will not achieve desired results because that simply means that an individual product which includes the merge module is being uninstalled, but there could be others installed that still depend on the merge module's database.
Scenario
Merge module X is installed with multiple product installers (ie. Product A, Product B, etc.). The merge module includes a sql database. When / how is it best to uninstall the sql database? I am assuming that creating a custom action with condition detecting if is an uninstall will not achieve desired results because that simply means that an individual product which includes the merge module is being uninstalled, but there could be others installed that still depend on the merge module's database.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 04, 2008
07:43 AM
I've never had to do this, but if the merge module contains other components with key files, I think you can use the MSI API to check to see what products are using those components, and then uninstall the database accordingly.
![](/skins/images/B841502EC6C60E3ACD181F0696AD21B9/responsive_peak/images/icon_anonymous_message.png)