Summary
Work with Command Events at Build Time
Synopsis
This article is intended to illustrate how to specify commands that run before, during and after builds with Prebuild, Precompression and Postbuild events in the InstallShield Premier product.
Discussion
The Windows command-line tools are used to perform various tasks related to the Windows operating system. An internal command is expected to be executed from the shell. Internal commands need to be "shelled out". An external command is expected to exist within an executable file on the client. For example, the COPY command is expected to be internal, while the XCOPY command is external.
The Events Tab on a release includes Prebuild, Precompression and Postbuild events. If it is possible to run a command from Start-Run it is expected the command can be included in the build process as an event.
Please reference the Microsoft documentation for information about various commands and see links below.
Example #1) Copy command "shelled out" to copy "Setup.ini" from directory "C:\" into the Disk1 directory of the current build. This example illustrates how a post build event can copy the specific *ini file to the build location. The switch '/C' is expected to carry out the command specified and then stops.
Cmd /C "Copy "C:\Setup.ini" "<ISReleasePath><ISProductConfigName>\<ISReleaseName>\DiskImages\Disk1\Setup.ini" "
Example #2) XCopy command to place the text file "somefile.txt" into the directory C:\myfilecopy.
XCopy c:\myfile\somefile.txt c:\myfilecopy /I
Related Documents
Specifying Commands that Run Before, During, and After Builds
Additional Information
The operating system Windows XP includes a help file ntcmds.chm. This file is expected to include details of some commands and their many switches. On an XP client use Start - Run:
hh ntcmds.chm
Windows Command Reference - Downloadable *.chm of the command-line tools used to perform various tasks related to Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 7, and Windows Vista.
Additional information can be found here: Command-line reference A-Z
Related Articles
Change Installer Name at Build Time in InstallAnywhere. 9Number of Views Verbosely Log a Command Line Build 9Number of Views Set Max Product Version (VersionMax) in the Upgrade table at build time. 5Number of Views Does Flexera offer static versions of libFlxComm64 and libFlxCore64 so that we can fully link our executable at build time? 10Number of Views How to Include Files and Folders with an Installer at Build Time Using Manifest Files 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago