Creating a Custom Condition for an Advanced UI or Suite/Advanced UI Installation

InstallShield 2016

Project • This information applies to the following project types:

Edition • The Advanced UI project type is available in the Professional edition of InstallShield. The Suite/Advanced UI project type is available in the Premier edition of InstallShield. For information about the differences between these two project types, see Advanced UI Projects vs. Suite/Advanced UI Projects.

When you are building a conditional statement for an exit, detection, eligibility, or feature condition in an Advanced UI or Suite/Advanced UI project, or for an action condition in a Suite/Advanced UI project, you can select from a number of different built-in types of checks that you want to be evaluated on target systems. Examples are operating system version, presence of a file or registry entry, and presence of an already installed product.

The built-in types of condition checks may not cover all of the scenarios that you want your Advanced UI or Suite/Advanced UI installation to evaluate on target systems. Therefore, InstallShield lets you create your own type of custom condition called an extension condition. An extension condition calls a C/C++ DLL that you have created.

For example, if you want to check for the existence of an IIS Web site, you can create a DLL that checks target systems and then include this DLL in your Advanced UI or Suite/Advanced UI project.

For guidance on how to create the extension condition DLL, see Creating an Extension Condition DLL for an Advanced UI or Suite/Advanced UI Project.

For instructions on how to incorporate the extension condition DLL in your project, see Adding an Extension Condition DLL to an Advanced UI or Suite/Advanced UI Project.

See Also

Extension Condition Settings

Building Conditional Statements in Advanced UI and Suite/Advanced UI Projects

Open topic with navigation