Advanced Tab

InstallShield 2013 » QuickPatch Project » General Information View » Build Settings

Project: This information applies to QuickPatch projects.

When you click Build Settings in the General Information view, InstallShield displays several tabs. The Advanced tab exposes a comprehensive set of build settings that you can configure for a QuickPatch.

Build Location

In the Build Location area, you can configure the following settings.

Build Location Settings

Property

Description

Build Location

Specify where you want your patch file built or browse for an existing folder.

Create Update.exe

Specify whether you want to create an Update.exe update launcher for the current QuickPatch package.

To learn when an Update.exe update launcher is required, see Patching Considerations.

List of Patch GUIDs to replace

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.

Create new “UpgradedImage” folder

This setting enables you to build your QuickPatch package with an existing UpgradedImage folder. To use this option, you must have built this package at least once (so that an UpgradedImage folder exists). Setting this option to No builds the package from the existing UpgradedImage folder. This lets you tweak the .msi package in the UpgradedImage folder and use that .msi data in a QuickPatch project. Setting this option to Yes (the default setting) regenerates the .msi file in the UpgradedImage folder every time that the package is built.

Generate MsiPatchOldAssembly tables

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.

Create patch sequencing entry

Specify whether you want to use patch sequencing for your QuickPatch. A patch sequence accounts for obsolete patches, superseded patches, and patches that have already been applied to the product. The sequence specifies the order that Windows Installer version 3.0 and later should apply patches to an installed product, regardless of the order in which they are provided to the target machine. For versions of Windows Installer earlier than version 3.0, the patch sequence is ignored, and any patches are applied to the product in the order that they are provided to the target machine.

Streamline QuickPatch

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:

•

The QuickPatch package removes an installed file.

•

The QuickPatch package removes or renames a registry key.

•

The QuickPatch package targets a non-streamlined QuickPatch image. That is, you cannot use QuickPatch streamlining if you select the check box in the History area of the General Information view for a QuickPatch that did not use QuickPatch streamlining. If you try to build a streamlined QuickPatch that targets one or more non-streamlined QuickPatch images, InstallShield displays a build warning, and it does not use streamlining.

Password Protect Launcher

To password-protect your QuickPatch package, select Yes, and then type a password for the Launcher Password setting. When you password-protect your QuickPatch package, any end user who wants to apply your QuickPatch must enter a case-sensitive password to launch your update.

This setting is applicable only to QuickPatch packages that use an Update.exe file.

Launcher Password

Type a password to protect your application. You must select Yes for the Password Protect Launcher setting to activate password protection.

When you password-protect your patch, any end user who wants to apply your patch must enter a case-sensitive password to launch your update.

This setting is applicable only to patches that use an Update.exe file.

Windows Installer Engine

In this area, you can configure the following settings for the Windows Installer engine:

Windows Installer Engine Settings

Property

Description

Include Windows Installer 3.1 engine

Specify whether the Windows Installer engine should be included with your patch package.

Engine Location

Select one of the following options:

•

Download Engine From The Web—If the Windows Installer engine needs to be installed, it is downloaded at run time.

•

Extract Engine From Update.exe—The build streams the Windows Installer engine into the Update.exe file, giving you a single file to distribute to your customers. At run time, the engine is extracted from the Update.exe file and installed if required.

•

Copy From Source Media—The build copies the Windows Installer engine into the same directory as the Update.exe file.

Windows Installer 3.1 engine URL

Specify the URL for the location of the engine. This is the location that the Update.exe file uses at run time to download the engine. The default URL location is a live site maintained by Flexera Software for your convenience.

Microsoft .NET Framework

In this area, you can configure the following settings for the Microsoft .NET Framework:

Microsoft .NET Framework Settings

Property

Description

Include In Build

Specify whether to include the Microsoft .NET Framework in your patch.

Engine Location

Select one of the following options:

•

Download Engine From The Web—If the .NET Framework needs to be installed, it is downloaded at run time.

•

Extract Engine From Update.exe—The build streams the .NET Framework into the Update.exe file, giving you a single file to distribute to your customers. At run time, the engine is extracted from the Update.exe file and installed if required.

•

Copy From Source Media—The build copies the .NET Framework into the same directory as the Update.exe file.

Engine URL

Specify the URL for the location of the .NET Framework. This is the location that the Update.exe file uses at run time to download the .NET Framework. The default URL location is a live site maintained by Flexera Software for your convenience.

Update Launcher Settings

In this area, you can configure the following settings for the Update.exe launcher:

Update Launcher Settings for a Patch

Property

Description

Company Name

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

The company 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.

Product Name

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.

Product Version

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

The product version 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.

Description

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.

If you want to override the default copyright notice for Update.exe with your product’s copyright notice, enter your product’s copyright notice.

The copyright notice 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.

Required Execution Level

Use the Required Execution Level setting to specify the minimum level required by your installation's Update.exe file for running the installation (the setup launcher, any InstallShield prerequisites, and the .msi file) on Windows Vista and later platforms. The available options are:

•

Administrator—Update.exe requires administrative privileges to run. Administrators must authorize it; non-administrators must authenticate as an administrator.

•

Highest Available—Update.exe prefers administrative privileges. Administrators must authorize it; non-administrators run it without administrative privileges.

•

Invoker—Update.exe does not require administrative privileges, and all users can run it without administrative privileges. Update.exe does not display any UAC messages prompting for credentials or for consent.

•

Use Previous Setup Manifest—The Update.exe manifest uses the same required execution level that was specified for the previous setup. This is the default option.

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.

Icon

To use your own icon for the Update.exe file, specify the fully qualified name of the file that contains the icon. To specify a file, type an absolute path or a path that is relative to a path variable, or click the ellipsis button (...) to browse to the file from within the Change Icon dialog box.

By default, the icon with index 0 is used; to specify a different icon, either select an icon in the Change Icon dialog box or append the icon’s index or resource ID (preceded by a minus sign) to the file name. For example, C:\Temp\MyLibrary.dll,2 indicates the icon with an index of 2, and C:\Temp\MyLibrary.dll,-100 indicates the icon with a resource ID of 100.

If you leave this setting blank, InstallShield uses a default icon for your Update.exe file.

Advanced Tab

InstallShield Help Library

June 2013