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: Custom action on final removal of merge module (or shared component)
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 11, 2008
09:13 AM
Custom action on final removal of merge module (or shared component)
I've created two custom actions in a merge module project. One performs an action involved in installing the components, the other performs an action to remove them. Both are a part of the ModuleInstallExecuteSequence table. The sequence numbers I associated with them are 6601 for the install step and 1501 for the removal step (somewhat arbitrary I wasn't sure what the best practice would have been in this case). For the install step I have the condition "Not Installed" and for the removal step I have the condition "Installed".
My question is regarding the removal step. If this merge module is used by more than one MSI used to install the software on a PC (the components are shared), how can I have my removal logic only executed when its associated components are no longer being used? As it stands today, my action is called regardless of whether the components are being removed or left because of dependencies from other installations. Do I have to implement the reference counting manually or is there a way to accomplish this automatically using conditions built into MSI?
My question is regarding the removal step. If this merge module is used by more than one MSI used to install the software on a PC (the components are shared), how can I have my removal logic only executed when its associated components are no longer being used? As it stands today, my action is called regardless of whether the components are being removed or left because of dependencies from other installations. Do I have to implement the reference counting manually or is there a way to accomplish this automatically using conditions built into MSI?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Aug 12, 2008
08:57 AM
Take a look at the help topic on conditional syntax. It shows how to check either the state or action to be taken on components and features. That may be what you're looking for.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)