InstallShield 2016 Express Edition
You can build a release from the command line using ISCmdBld.exe for Express projects.
Syntax
The following statement illustrates running ISCmdBld.exe to build the release Othello Beta:
ISCmdBld.exe -p "C:\InstallShield 2016 Projects\My Othello Project\Othello.ise" -r "SingleImage" -c COMP
The first parameter in the example above, starting with -p, is the path to the .ise file that you would like to build. Next, -r Othello Beta is the type of media. The parameter -c COMP specifies that you would like your package to be compressed into one file.
If a command-line build completes without any errors, InstallShield sets the environment variable ERRORLEVEL to 0. If an error occurs during a command-line build, ERRORLEVEL is set to 1. If ERRORLEVEL is set to any other value, this typically indicates an invalid parameter was passed to ISCmdBld.exe, and the specific cause of the error is displayed in the Command Prompt window in which ISCmdBld.exe was running.
Command-Line Parameters
ISCmdBld.exe supports the following command-line parameters.
|
Parameter |
Description |
||||||||||||||||||||||||
|
-b <build location> |
The fully qualified path to the folder where you want the output folders and files to be placed. UNC paths are acceptable. The built installation’s files will be located in the DiskImages\Disk1 subfolder of the location that you specify. Enclose long file names in quotation marks. This parameter is optional. |
||||||||||||||||||||||||
|
-c <compression option> |
This parameter allows you to specify whether you want to have your release compressed into one file or remain uncompressed in multiple files. The valid arguments for this parameter are COMP and UNCOMP. To specify that your release be compressed into one file, use the COMP argument. If you do not want your release compressed, use the UNCOMP argument. This parameter is optional. If the release name already exists, the configuration will be based on what was specified in the IDE. If this is ignored for a new release, the new package will be uncompressed. |
||||||||||||||||||||||||
|
-e <Y/N> Setup Package |
Use this parameter to specify whether you want to create Setup.exe along with your installation project. Specify Y to build Setup.exe, or N to create just an installation package. This parameter is optional. |
||||||||||||||||||||||||
|
-i <.ini file path> |
Instead of passing all of your parameters on the command line, you can include them in an initialization (.ini) file and call that file from the command line. For more information, see Passing Command-Line Build Parameters in an .ini File. Absolute and relative paths are acceptable. Enclose long file names in quotation marks. This parameter is optional. |
||||||||||||||||||||||||
|
-o <merge module search path> |
This parameter specifies one or more comma-delimited folders that contain the merge module files (.msm) that are referenced by your project. InstallShield provides additional ways for specifying the folders that contain merge modules. For more information, see Specifying the Directories that Contain Merge Modules. |
||||||||||||||||||||||||
|
-p <project location> |
Pass the path to the project (.ise) file. This path can be fully qualified, relative, or just the file name. UNC paths are also acceptable. If only the project file name is passed, the file is retrieved relative to the current working directory. For example: IsCmdBld.exe -p "C:\InstallShield 2016 Projects\MyProject1\MyProject1.ise" This is the only required parameter. Enclose long file names in quotation marks. |
||||||||||||||||||||||||
|
-prqpath <InstallShield prerequisite search path> |
This parameter specifies one or more comma-delimited folders that contain the InstallShield prerequisite files (.prq) that are referenced by your project. InstallShield provides additional ways for specifying the folders that contain InstallShield prerequisite files. For more information, see Specifying the Directories that Contain InstallShield Prerequisites. |
||||||||||||||||||||||||
|
-r <release type> |
Use this parameter to specify the release type (for example, SingleImage or WebDeployment). Valid options are:
If you do not specify this parameter and build from the command line, the command-line build uses the last release type built in the IDE as the release type. If you have never built a release in the IDE, the command-line build uses the SingleImage release type. This parameter is optional. |
||||||||||||||||||||||||
|
-s |
This parameter allows you to build your release in silent mode. Silent builds are useful if you want to run the build without displaying any errors or warning messages. This parameter is optional. |
||||||||||||||||||||||||
|
-u |
This parameter enables you to upgrade—but not build—your release. You can use this parameter to upgrade an installation project that you created with an earlier version of InstallShield. This parameter is optional. |
||||||||||||||||||||||||
|
-w |
This parameter treats warnings that occur during the build process as errors. Each warning increments the error count by one. This parameter is optional. |
||||||||||||||||||||||||
|
-x |
If you want the build to stop when it encounters an error, use the -x parameter. If you want the build to stop when it encounters a warning, use this parameter in conjunction with the -w parameter. This parameter is optional. |
||||||||||||||||||||||||
|
-y <product version> |
This parameter enables you to specify a product version from the command line. This is especially helpful if you want to increment the build version (the third field) of the product version. For example, to set the product version to 1.0.5: ISCmdBld.exe -y "1.0.5" For information on valid product version numbers, see Specifying the Product Version. This parameter is optional. |
See Also
Building from the Command Line
Passing Command-Line Build Parameters in an .ini File
InstallShield 2016 Express Edition Help LibraryMay 2017 |
Copyright Information | Flexera Software |