Right, I'm not sure you can specify the order in which Installer classes are called. For that reason, explicitly calling a managed-code custom action or the like would presumably be required.
It's possible via a postbuild step that reorders the sequence tables but I really, really, really, really NEVER use Installer class custom actions. I wouldn't wish them on my worst enemies. Checkout WiX DTF instead.
I ended up creating the custom actions myself by looking in the msi-file how InstallShield does it. I placed the install, commit and rollback CA's immediately before "Service Start" and the uninstall immediately before "msiUnpublishAssemblies". Then it worked 🙂
I have submitted an enhancement request to InstallShield, that it should be possible to specify the order of execution.
Personally I think a better feature request would be to remove Installer class custom actions all together.
You may have gotten it `to work` for today, but Installer class custom actions are fragile and the WILL give you problems one day in the future. I'd bet a pay check on that.
Managed custom actions aren't evil, Installer class custom actions are. Check out DTF.
