I have a msi that has a custom action and it works fine when I install it. But if I use this msi in a chained installation ("master" installation installs it), its custom action is not run. Does anyone know why?
There's no fundamental reason I'm aware of. It could well depend on the condition on the custom action being evaluated differently inside a multiple package transaction, it could be related to other environmental differences causing the implementation of the custom action to fail, or other problems. Have you examined a verbose log for any information related to the action - either whether it executes, or what the custom action succeeds or fails to do?
