Hello,
I'm not sure why you encountered this behavior. I've tested your scenario but I cannot replicate it.
Also, I've attached a sample which implement your scenario.
I've used the predefined
Execute inline script code custom action with sequence on the
Wizard Dialogs Stage. This custom action is basically a small VBScript or JScript that is ran during the install process.
In order to
launch a vbs file which is not among my project files I've used the predefined
Launch attached file custom action with sequence. Using this type of custom action you can execute an application (EXE or DLL) or run a script (VB or Java script) which is not among your project files. This source file will be embedded in the MSI file but will not be deployed at install time with the other application files.
Maybe the
Why does my VBScript custom action fail to run? artcile and
How do I debug a .VBS custom action? can help you.
Please let us know if that helped.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging