Build Events

Build events let you run custom applications as an integral part of your build process. To access your build events:

• Press SHIFT+CTRL+F11.
• On the Project tab, in the Manage group, click Project Settings.
• On the MSIcode tab, in the Compile group, click Project Settings.

Events Node

This page lets you configure your build events. The various kinds of build events, along with their triggers, are explained below:

• Pre-Build Event: Triggers immediately after your setup build folder has been cleared, in preparation for a new build. This event triggers for all types of setups and patches being built.
• Post-Build Event: Triggers immediately after your setup build folder has been fully populated with uncompressed data (and after any code signing where applicable). This event triggers for all types of setups and patches being built.
• Pre-Compress Event: Triggers immediately before compression is about to begin on your setup build folder. This event triggers only for compressed setups and patches.
• Post-Compress Event: Triggers immediately after compression has completed on your setup build folder (and before any code signing where applicable). This event triggers only for compressed setups and patches.
• Pre-Wrap Event: Triggers immediately before a compressed setup is to be wrapped inside a Group Policy MSI file. This event triggers only for compressed setups and patches.
• Post-Wrap Event: Triggerrs immediately after a compressed setup has been wrapped inside a Group Policy MSI file (and after any code signing where applicable). This event triggers only for compressed setups and patches.

Please note that the post-build event does not trigger for a patch build until after the latest version base setup has been built, all patch references have been extracted, and the upgrade patch has been created.

Commands

Specify one command on each line of this field.

You may run as many custom applications as necessary for your build process.

Enclose paths to applications containing spaces within double quotes (").

Enclose application parameters containing spaces within double quotes as well ("), otherwise each space delineates a new application command line parameter.

If you use compiler variables in this field, most commonly to reference the project folder (#PROJDIR#) and the InstallAware toolchain folder (#IADIR#), they will be resolved to their literal values during a build process.

Abort build on error (if any command returns non-zero result)

Check this box to break the setup build process when any invoked application returns a non-zero error code as the exit code of its process. Non-zero process exit codes typically indicate a failure in the exiting application.

If this box is not checked, applications participating in the setup build process cannot abort an ongoing build.