Hello, I created a VB Script custom action and added it to the execution sequence right after the Install Files standard action. The reason is that I want to register some DLL file using regsvcs.exe.
This never happened. When I debugged the sequence, I saw that right after InstallInitialize it jumped directly to ISComponentServiceCosting and afterwards directly to my custom action and then to the InstallFinalize action!
Only then, it resumed ProcessComponents, UnpublishComponents, etc. until it reached Install files action.
Why???
What do I have to do in order to activate my custom action only after the Install files standard action?
I use DEV Studio 9, Basic MSI Project. I know it is not the right forum but there is no such a forum... 😄
If you want actions to run after system changes have taken place (files installed, and that sort of thing), you'll want the action to be scheduled for "deferred execution".
