09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8: Organizing Files for Your Installation<br />

Including Redistributables in Your Installation<br />

installation, the Windows Installer engine evaluates only the feature prerequisites and—if appropriate—installs them in the<br />

order that you specified.<br />

To learn about the differences between setup prerequisites and feature prerequisites (which are the two types of<br />

<strong>InstallShield</strong> prerequisites), see Setup Prerequisites vs. Feature Prerequisites.<br />

Configuring a Release that Includes <strong>InstallShield</strong> Prerequisites<br />

When you package an installation that includes <strong>InstallShield</strong> prerequisites, you can use any one of the<br />

following methods for supplying the <strong>InstallShield</strong> prerequisite files to end users:<br />

• Store the <strong>InstallShield</strong> prerequisite files on the source media.<br />

• Compress the <strong>InstallShield</strong> prerequisite files into Setup.exe, to be extracted at run time, as needed.<br />

• If necessary, your installation can download the <strong>InstallShield</strong> prerequisite files that are included in<br />

your project from the URL that is specified in the <strong>InstallShield</strong> prerequisite file (.prq) for each<br />

prerequisite.<br />

You can specify different methods for each <strong>InstallShield</strong> prerequisite in your project. To learn more, see<br />

Specifying a Run-Time Location for a Specific <strong>InstallShield</strong> Prerequisite.<br />

You can also override individual methods at the release level if you want all of the <strong>InstallShield</strong><br />

prerequisites in a release to be available through the same method. For more information, see Specifying<br />

the Run-Time Location for <strong>InstallShield</strong> Prerequisites at the Release Level.<br />

<strong>Edition</strong>: <strong>InstallShield</strong> Premier <strong>Edition</strong> and <strong>InstallShield</strong> Professional <strong>Edition</strong> enable you to configure an <strong>InstallShield</strong><br />

prerequisite so that it is installed either before or after any installation of the Windows Installer engine and the .NET<br />

Framework.<br />

Specifying the Directories that Contain <strong>InstallShield</strong> Prerequisites<br />

The default location for <strong>InstallShield</strong> prerequisite files (.prq) is:<br />

<strong>InstallShield</strong> Program Files Folder\SetupPrerequisites<br />

<strong>InstallShield</strong> lets you specify additional or alternative locations on your local machine, or on a network.<br />

This flexibility enables you to store <strong>InstallShield</strong> prerequisites in source code control and to share a<br />

common set of <strong>InstallShield</strong> prerequisites with other team members.<br />

<strong>InstallShield</strong> offers several ways for specifying the search paths for <strong>InstallShield</strong> prerequisite files (.prq):<br />

• If you are editing or building from within <strong>InstallShield</strong>, use the Prerequisites tab on the Options<br />

dialog box—which is displayed when you click Options on the Tools menu—to specify a commadelimited<br />

list of machine-wide folders and current-user folders.<br />

• If you are building from the command line with ISCmdBld.exe, use the -prqpath parameter to<br />

specify a comma-delimited list of folders.<br />

If you use an .ini file to specify ISCmdBld.exe parameters, you can use the PrerequisitePath<br />

parameter in the [Mode] section of your .ini file to specify a comma-delimited list of folders.<br />

• If you are building through MSBuild or Team Foundation Server (TFS), use the PrerequisitePath<br />

parameter on the <strong>InstallShield</strong> task. This parameter is exposed as the ItemGroup<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1800-UG01 177

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

Saved successfully!

Ooh no, something went wrong!