Setup Factory for Windows Installer

Unattended Build Options

The following command line options are supported by Setup Factory for Windows Installer's design environment for an unattended build process:

Note: The unattended build returns 0 as a process return code if successful, or non-zero if not. You can use this return code to make your batch files respond to the success or failure of the build process.

/BUILD

Tells Setup Factory for Windows Installer to build the project file passed in on the cmd line or from a batch file. For example:

"C:\Program Files\Setup Factory for Windows Installer\Setup Factory.exe" /BUILD "C:\TestProj.sufproj"

/LOG:<<log file path>>

Specifies a log file to output build status to.  If the file exists, the output will be appended to it. If the file does not exist, it will be created. For example:

"C:\Program Files\Setup Factory for Windows Installer\Setup Factory.exe" /BUILD "C:\TestProj.sufproj" "/LOG:C:\output\Log.txt"

/STDOUT

Makes the build status go to the standard output device (console). For example:

"C:\Program Files\Setup Factory for Windows Installer\Setup Factory.exe" /BUILD "C:\TestProj.sufproj" "/STDOUT"

/VARS:<<ini file path>>

Lets you specify an INI file that contains build variables to override the ones in the project. You can define as many build variables as you want in the INI file, with each variable on a separate line beneath the [Variables] section. Each variable that is defined in the INI file must already be defined in the project file. For example:

 

[Variables]

OUTPUTDIR=C:\Output\Foobar 2002\Release

SETUPNAME=foobar2002setup

BUILD=release

When you use the /VARS option along with /BUILD, the specified project file is loaded into Setup Factory for Windows Installer, the variables described in the specified unattended-build INI file are set, and the setup is generated-all without any interaction.

 

For example:

"C:\Program Files\Setup Factory for Windows Installer\Setup Factory.exe" /BUILD "C:\sufproj" "/VARS:C:\MyProj\Config.ini"