Passing Command-Line Build Parameters in an .ini File

InstallShield 2012 Spring Express Edition

If you want to pass numerous parameters during a command-line build, or if you consistently pass the same parameters, it might be convenient to use an .ini file. The following statement illustrates running ISCmdBld.exe to build a release with parameters as specified in the MySetup.ini file.

ISCmdBld.exe -i "C:\InstallShield 2012 Spring Projects\MySetup.ini"

You need to include the same information in the .ini file as you would if you were passing the parameters at the command line. There are four sections for this file:

[Project]—In this section, include entries for the path to the project file (.ise), as well as the name of the product configuration. If you are building a patch, include an entry for the name of the patch configuration that you are building.
[Release]—In this section, include entries for release configuration information such as the compression type (compressed or uncompressed), build flags, Setup.exe settings, and the release name.
[Mode]—In this section, include any of the available optional entries, such as the Silent=yes entry if you want to build your release while suppressing any build errors or warning messages. This section also lets you indicate whether a log file should be created.
[BuildLocation]—In this section, you can optionally specify the release output location.

Not all sections are required. As with passing parameters directly from the command line, parameters for requirements such as silent build and build location are optional. In the example .ini file below, these parameters are in the [Mode] and [BuildLocation] sections. You can omit these entries from your .ini file if you want to accept the defaults. By default, no log file is created, the installation is not run in silent mode, and your release is created in the project location that is specified on the File Locations tab of the Options dialog box.

Sample .ini File

The following tables contain sample entries from each of the four sections in a sample .ini file. The first column of each table shows a sample entry. The other columns provide the corresponding command-line parameter and description.

Entries in the [Project] Section

Sample Entries in the [Project] Section of the .ini File

Entry

Corresponding ISCmdBld.exe Command-Line Parameter

Description

Name="C:\InstallShield 2012 Spring Projects\Othello.ise"

-p

Path to the .ise file.

Product=Othello

 

Name of your product. This entry lets you override the value that is specified in the General Information view.

Entries in the [Release] Section

Sample Entries in the [Release] Section of the .ini File

Entry

Corresponding ISCmdBld.exe Command-Line Parameter

Description

Configuration=COMP

-c

Compressed vs. uncompressed.

Name=Othello Beta

-r

Release name.

SetupEXE=yes

-e

Creates a Setup.exe file.

Entries in the [Mode] Section

Sample Entries in the [Mode] Section of the .ini File

Entry

Corresponding ISCmdBld.exe Command-Line Parameter

Description

Silent=yes

-s

Runs in silent mode.

MergeModulePath="C:\..."

-o

Search path for merge modules (.msm files).

For more information, see Specifying the Directories that Contain Merge Modules.

PrerequisitePath="C:\..."

-prqpath

Search path for InstallShield prerequisite files (.prq).

For more information, see Specifying the Directories that Contain InstallShield Prerequisites.

See Also