09.12.2012 Views

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

History<br />

Custom Action<br />

Table 24-76: Update Launcher Settings (cont.)<br />

Property Description<br />

Chapter 24: View Reference<br />

QuickPatch Projects<br />

Required Execution Level Use the Required Execution Level setting to specify the minimum level required by<br />

your installation's Update.exe file for running the installation (the setup launcher,<br />

any <strong>InstallShield</strong> prerequisites, and the .msi file) on Windows Vista and later<br />

platforms. The available options are:<br />

• Administrator—Update.exe requires administrative privileges to run.<br />

Administrators must authorize it; non-administrators must authenticate as an<br />

administrator.<br />

• Highest Available—Update.exe prefers administrative privileges.<br />

Administrators must authorize it; non-administrators run it without<br />

administrative privileges.<br />

• Invoker—Update.exe does not require administrative privileges, and all users<br />

can run it without administrative privileges. Update.exe does not display any<br />

UAC messages prompting for credentials or for consent.<br />

• Use Previous Setup Manifest—The Update.exe manifest uses the same<br />

required execution level that was specified for the previous setup. This is the<br />

default option.<br />

If the Create Update.exe check box is selected, <strong>InstallShield</strong> embeds an application<br />

manifest in the Update.exe launcher. This manifest specifies the selected execution<br />

level. Operating systems earlier than Windows Vista ignore the required execution<br />

level.<br />

If the Create Update.exe check box is cleared, <strong>InstallShield</strong> does not embed the<br />

Windows application manifest in an Update.exe launcher.<br />

For more information, see Minimizing the Number of <strong>User</strong> Account Control Prompts<br />

During Installation.<br />

The History item in the General Information explorer within the General Information view presents a<br />

synopsis of your QuickPatch project. It lists all of the associated releases, enabling you to specify which<br />

ones should be patched by the current QuickPatch project.<br />

Caution: If you open and modify any of the releases listed in the History, your latest project will not work since<br />

intermediate data shared across the releases in the History may have been lost or altered.<br />

Note: When you specify which releases from the History to patch, <strong>InstallShield</strong> looks for specific versions associated with<br />

each release to identify it.<br />

The Custom Action item in the General Information explorer within the General Information view lists<br />

the custom actions that are defined in the original installation project for which you are creating a patch.<br />

It enables you to specify which actions should be executed by the current QuickPatch project.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Spring</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1900-UG00 605

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!