This view allows you to include existing installers in your package, to enable Windows features or set specific Windows Server roles.
Existing installers can be added in multiple ways, depending on the moment you want to execute them:
- Frameworks - frameworks and runtimes required by your package or application (e.g. .NET Framework, SQL Server, etc). They are launched by an EXE bootstrapper before your MSI is launched.
- Pre-install - additional packages that are installed before the MSI is launched. The UI for these prerequisites can be customized from the Pre-install UI section from the Dialogs page.
- Feature-based - additional packages which are handled as features during your main installation. They are launched right before the main installation after pressing the button.
- Chained - packages embedded in your MSI using native Windows Installer 4.5 support. They are ignored on machines with older Windows Installer versions.
- Post-install - feature-based prerequisites which are launched after your main installation. They are also handled by the installation user interface.
You can change when a prerequisite is executed by dragging it over the appropriate folder (Frameworks, Pre-install, Feature-based or Post-install).
Frameworks and Pre-install prerequisites are handled by our EXE bootstrapper. This is why the corresponding option must be checked in the Configuration Tab page.
All setup files used by a prerequisite can be bundled with your package or placed online and accessed through a URL. During install, if the prerequisite is not found it will be automatically installed.
Adding predefined prerequisites
Select Packages tree item to display the Frameworks and Runtimes page. You can then check the prerequisites you want to include in your package.
In Frameworks and Runtimes page you can also configure global prerequisite options.
To make sure that the target machines can run your installation package, you can include Windows Installer as a prerequisite. Windows Installer predefined prerequisites use special setup file locations. When building your project, the prerequisite installation package is downloaded automatically. If the download fails or you cancel it, an error message will be displayed and the build process is aborted.
Adding bundled prerequisite software
Use the Insert key. You will be prompted to pick the prerequisite setup files.toolbar button, “New Package Prerequisite” context menu item or
Adding downloadable prerequisite software
Use thetoolbar button or “New URL Prerequisite” context menu item to add the download URL of the prerequisite. This type of prerequisite is created with default settings, so you need to configure it manually.
Adding chained packages
Use thetoolbar button or context menu item. Chained packages are handled by the actual installation process and are launched when the progress bar is shown.
Chained packages require Windows Installer 4.5 or higher. For older Windows Installer versions they are ignored.
Specify which builds will contain a prerequisite or chained package
Use the “Builds...” context menu item. A dialog with all MSI builds will be displayed. This option is shown only if multiple builds were created in Builds page.
Adding a prerequisite from repository
Use the “Add From Repository” context menu item. A submenu with all the available repository prerequisites will be displayed.
This option is shown only if there is at least one prerequisite in repository.
Exporting a prerequisite in repository
Select the prerequisite you want to export and use the “Move To Repository” context menu item.
You can read more about the prerequisites repository in this article.
Editing a prerequisite or chained package
When selecting a prerequisite or chained package, its properties pane will be displayed. In this pane you can configure all available package settings.
Use the Delete key while a prerequisite or chained package is selected.toolbar button, the “Delete” context menu item or press the
Reordering prerequisites and chained packages
The order in which the prerequisites and chained packages are displayed is the order in which they will be installed on the target machine. The Shift + Up keys will move a package up. The context menu item or Shift + Down keys will move it down.context menu item or
Adding a Windows Features bundle
Use thetoolbar button or “New Windows Feature bundle” context menu item.
Editing a Windows Features bundle
When selecting a Windows Features bundle, its properties pane will be displayed. In this Windows Features pane you can configure all available settings.
Removing a Windows Features bundle
Use the Delete key while a Windows Features bundle is selected.toolbar button, the “Delete” context menu item or press the
Windows Server Roles
Roles selected in this view only apply when running the package on a Windows Server. They will be ignored on any other OS type.
This feature is available for Enterprise or above project types.
Adding a Windows Server Role
Select Windows Server Roles tree item, then check the roles you want to include in your package. The roles are grouped by the earliest supported version of the target server OS.
Editing a Windows Server Role
When selecting a Windows Server Role, its properties pane will be displayed. In this Windows Server Roles pane you can configure all available settings.
Removing a Windows Server Role
Use the Delete key while a Windows Server Role is selected.toolbar button, the “Delete” context menu item or press the