Custom Action in merge module still runs if merge module not installed.
This is still an issue with IS Spring 2012 - I have trouble seeing how this is anything other than a bug, you can't not include the merge module but still run it's custom actions, that makes no sense, it's an atomic entity.
Has a bug been logged for this issue??
This has been referenced in many posts going back, most recently by a quick search:
In case another description is needed of the bug, having an msi include a merge module conditionally will not regard the conditions of the merge module (whether it's being installed or not!!) when checking whether to run its custom actions. You result with an action that executes when the merge module should not be installed.
