Importing Dialogs from an .isd File

InstallShield 2016

InstallShield enables you to import a dialog into your installation project. The file for the dialog (.isd file) can be stored in a repository, or it can be stored in some other location.

To import a dialog into your project from an .isd file:

In the View List under User Interface, click Dialogs.

In the Dialogs explorer, right-click the dialog and then click Import Dialog. The Import Dialog dialog box opens.

Do one of the following:

•

In the Repository Items box, click the dialog that you want to add to your project.

•

If the file for the dialog box (.isd file) that you want to import is not stored in the repository, click the Browse button to select it.

Click OK.

InstallShield adds a copy for each supported language to your project.

Note • When you import a dialog, make sure that any string identifiers, properties, and actions referenced by the dialog are present in the new installation project.

Resolving Conflicts

When you import a dialog, InstallShield checks to make sure that the name of the dialog and its controls are unique—as required by Windows Installer. You cannot import a dialog with the same name as an existing dialog because InstallShield assumes that you are trying to import an identical dialog.

If you try to import an .isd file that uses the names of controls or string identifiers that already exist in your installation project, InstallShield asks how you want to resolve those conflicts. You can either overwrite the existing values or skip the imported values in order to leave the existing ones.

Displaying Dialogs During Installation

Adding a dialog to a project does not mean that the dialog will be displayed in the installation. For information on inserting the dialog into one or more of the project’s sequences, see Displaying Dialogs During Basic MSI Installations.

Importing Dialogs from an .isd File

InstallShield 2016 Help Library

August 2016