Advanced Tab

Select the file format that you want to use for your project file (.ism). Available options are:

Note • Both project file formats let you build releases from the command line.

To replace one or more earlier installed patches with the current QuickPatch, set this property to the patch GUIDs of those patches, and separate each with a comma. For example:

{C86838C9-DEDC-4451-B96F-94AFB9460F15},{C8633E5B-AC44-45d8-B487-C68B3B1F60D6}

Setting this property is typically not required, even if you have several QuickPatch projects in the History. However, if your QuickPatch project does not overwrite files added in an earlier QuickPatch project, it may be necessary to set this property.

If you do not know the GUID of a patch that you want to replace, click this property and then click the ellipsis button (...). Select the patch (.msp or .exe file), and InstallShield will add the corresponding GUID to this property.

Specify whether to automatically generate entries for the MsiPatchOldAssemblyFile and MsiPatchOldAssemblyName tables, which allow a patch package that is running under Windows Installer 3.0 and later to patch an assembly in the global assembly cache (GAC) without making a run-time request for the original installation source. For more information, see Patching Assemblies in the Global Assembly Cache.

Specify whether you want InstallShield to streamline the creation of your QuickPatch package to build as simple a package as possible. The default value is Yes.

The goal of QuickPatch streamlining is to generate a QuickPatch package that has fewer new subfeatures and custom actions than a non-streamlined QuickPatch package.

For example, if your QuickPatch project includes a new file or registry entry and InstallShield does not use QuickPatch streamlining, InstallShield creates a new subfeature for that file or registry entry. InstallShield also adds one or more prebuilt InstallShield custom actions to work around certain Windows Installer patch requirements. However, if InstallShield does use QuickPatch streamlining, the file or registry entry is added to an existing feature, and no special prebuilt InstallShield custom actions are required.

Note • InstallShield cannot streamline the creation of a QuickPatch package in the following scenarios:

Select one of the following options:

Select one of the following options:

If you want to override the default product name for Update.exe with your product name, enter your product name.

The product name is displayed on the Properties dialog box for the update launcher; this Properties dialog box opens when end users right-click the Update.exe file and then click Properties.

To learn more, see Customizing File Properties for the Update Launcher.

If you want to override the default description for Update.exe with your own description, enter the appropriate description.

The description is displayed on the Properties dialog box for the update launcher; this Properties dialog box opens when end users right-click the Update.exe file and then click Properties.

To learn more, see Customizing File Properties for the Update Launcher.

Use the Required Execution Level setting to specify the minimum level that is required by your project’s Update.exe file for running on Windows Vista and later platforms. The available options are:

For InstallScript MSI projects, and for Basic MSI projects if the Create Update.exe check box is selected, InstallShield embeds an application manifest in the Update.exe launcher. This manifest specifies the selected execution level. Operating systems earlier than Windows Vista ignore the required execution level.

If the Create Update.exe check box is cleared for a Basic MSI project, InstallShield does not embed the Windows application manifest in an Update.exe launcher.

For more information, see Minimizing the Number of User Account Control Prompts During Installation.