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.

Chapter 16: Building, Testing, and Distributing Installations<br />

Configuring and Building Releases<br />

Task To specify the required execution level for a release:<br />

1. In the View List under Prepare for Release, click Releases.<br />

2. In the Releases explorer, click the release that you would like to configure.<br />

3. Set the Required Execution Level to the appropriate setting.<br />

4. Click the Setup.exe tab.<br />

The available options are:<br />

• Administrator—Setup.exe requires administrative privileges to run. Administrators must provide<br />

consent, and non-administrators must provide credentials.<br />

• Highest available—Setup.exe prefers administrative privileges. Administrators must provide consent<br />

to run it; non-administrators run it without administrative privileges.<br />

• Invoker—Setup.exe does not require administrative privileges, and all users can run it without<br />

administrative privileges. Setup.exe does not display any UAC messages prompting for credentials<br />

or for consent. This is the default option.<br />

If the Setup Launcher setting is set to Yes, <strong>InstallShield</strong> embeds a Windows application manifest in the<br />

Setup.exe launcher. This manifest specifies the selected execution level. Operating systems earlier than<br />

Windows Vista ignore the required execution level.<br />

If the Setup Launcher setting is set to No, <strong>InstallShield</strong> does not embed the Windows application<br />

manifest in the Setup.exe launcher.<br />

The benefit of elevating the required execution level is that privileges can be elevated only once if<br />

necessary to run Setup.exe, and that these privileges can be carried over to all of the installation’s<br />

prerequisites and the .msi file without requiring multiple prompts for approval. Thus, if two of your<br />

prerequisites require administrative privileges, for example, you can change this setting to<br />

Administrator, and then end users are prompted only once during the installation, before Windows<br />

Installer runs the Setup.exe file. Note, however, that if you elevate the privileges and also launch the<br />

application at the end of the installation, the elevated privileges are carried over to the application. In<br />

most cases, running an application with elevated privileges on Windows Vista and later platforms is<br />

discouraged.<br />

Note that an end user’s installation experience is more secure when installations are run with only the<br />

permissions that they need. Unless an application is designed to be run only by system administrators, it<br />

should be run with the least privilege.<br />

Preparing Your Installation for Internet Distribution<br />

The way in which consumers receive software is rapidly changing. Before the advances in Internet<br />

technology and the introduction of high-speed connections, all software was shipped on some type of<br />

removable medium, such as floppy disks or CD-ROMs. Today, many people download their software<br />

directly from the Internet. In order to take advantage of this time- and money-saving software<br />

distribution process, you must package your installation in an easily downloadable and installable<br />

manner.<br />

There are several criteria that your Web-ready installation may need to meet:<br />

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

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

Saved successfully!

Ooh no, something went wrong!