Custom Action Method to Call .bat or vbs file
Would any of you veterans show me how to call a .vbs or .bat with a custom action inside installshield before I compile as an MSI?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Coriolus
16 years ago
I don't use Install Shield, I use WinINSTALL Packager Pro but here are some universal guidelines to help.
1./ After you have your completed batch file or VBS script copy it to your package's directory.
- Create a new component off the MAIN package feature
- Give the source directory and target directory of teh file in question
Source = the place you copied the file to
Target = the place on the target system you want the MSI to copy the file to and execute it.
- Give the Key path to the file
2./ Once that is completed you can create a Custom Action that will execute the Batch/VBS. I am sure Install Shield must have a wizard for this. Give your custom action a name you will recognize.
3./ Add your custom action to the Execute Sequence, this must be just before the 'InstallFinalize' action so choose your sequence number correctly as to not create any conflicts.
Also add 'NOT Installed' as a condition of the custom action so it runs only on installation. Unless you want it to run on both install or uninstall.
That should do it. Good luck!
1./ After you have your completed batch file or VBS script copy it to your package's directory.
- Create a new component off the MAIN package feature
- Give the source directory and target directory of teh file in question
Source = the place you copied the file to
Target = the place on the target system you want the MSI to copy the file to and execute it.
- Give the Key path to the file
2./ Once that is completed you can create a Custom Action that will execute the Batch/VBS. I am sure Install Shield must have a wizard for this. Give your custom action a name you will recognize.
3./ Add your custom action to the Execute Sequence, this must be just before the 'InstallFinalize' action so choose your sequence number correctly as to not create any conflicts.
Also add 'NOT Installed' as a condition of the custom action so it runs only on installation. Unless you want it to run on both install or uninstall.
That should do it. Good luck!
Posted by:
nrkres
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.