Hi,
While I was trying to divide my setup in parents and children by the help of merge modules,
I came across to a problem within the custom actions.
After investigating the issue, I found out that if I am adding custom actions to a merge module,
that the custom actions seem to be always executed even during uninstallation even though I put my actions into the install stage.
As a consequence the uninstall fails because my custom action (for the installation stage) requires installed files which are already uninstalled.
The question is why is the custom action within the merge module executed eventhough the stage is not matching.
If I put the custom actions to the parent, it works fine BUT thats not what I intended to do and also then you cannot use custom actions in merge modules if you cannot rely on the execution state.
Is there anything I can do to fix that problem ?
Thanks,
Holger
FOLLOW US
Get the latest news in Application Packaging