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 />

<strong>InstallShield</strong>PrerequisitePath when the default targets file is used. To specify multiple paths, use an<br />

ordered array of paths.<br />

Instead of using hard-coded paths, you can use path variables in paths, as in the following example:<br />

\SetupPrerequisites,\MyCustomPrerequisites<br />

The Redistributables view lists the names of the <strong>InstallShield</strong> prerequisites that correspond with the .prq<br />

files that are present in the various search paths that are specified on the Prerequisites tab of the Options<br />

dialog box. If the same .prq file is in multiple search paths, <strong>InstallShield</strong> shows only the first instance<br />

that it encounters. <strong>InstallShield</strong> first searches each path that is listed in the per-user setting on the<br />

Prerequisites tab. Then, <strong>InstallShield</strong> checks each path that is listed in the machine-wide setting.<br />

At build time, if your project includes one or more <strong>InstallShield</strong> prerequisites, <strong>InstallShield</strong> searches the<br />

specified locations and includes the appropriate <strong>InstallShield</strong> prerequisites in your release as needed. If<br />

the same .prq file is in multiple search paths, <strong>InstallShield</strong> includes in the build only the first instance<br />

that it encounters. It uses the following order to search for .prq files:<br />

1. <strong>InstallShield</strong> checks the paths that are specified through the -prqpath command-line parameter, the<br />

PrerequisitePath .ini file parameter, or the PrerequisitePath parameter on the <strong>InstallShield</strong> task.<br />

2. <strong>InstallShield</strong> checks each path that is listed in the per-user setting on the Prerequisites tab.<br />

3. <strong>InstallShield</strong> checks each path that is listed in the machine-wide setting on the Prerequisites tab.<br />

4. If no paths are specified in any of the aforementioned locations, <strong>InstallShield</strong> checks the default<br />

location (<strong>InstallShield</strong> Program Files Folder\SetupPrerequisites).<br />

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

<strong>InstallShield</strong> enables you to specify a different run-time location for each <strong>InstallShield</strong> prerequisite in<br />

your project.<br />

Task To specify a different location for each <strong>InstallShield</strong> prerequisite in your installation:<br />

1. In the View List under Specify Application Data, click Redistributables.<br />

2. Select the check box for one of the <strong>InstallShield</strong> prerequisites that you want to include in your<br />

installation.<br />

3. Right-click the <strong>InstallShield</strong> prerequisite and click Properties. The <strong>InstallShield</strong> Prerequisites<br />

Properties dialog box opens.<br />

4. In the Build Location list, click the appropriate option.<br />

Note that the location that you specify can be overridden at the release level. To avoid overriding the<br />

value that you selected for an individual <strong>InstallShield</strong> prerequisite, the <strong>InstallShield</strong> Prerequisites<br />

Location setting at the release level setting must be set to Follow Individual Selections. For more<br />

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

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

When <strong>InstallShield</strong> builds a Setup.exe file for a project that does not include any prerequisites, it starts<br />

with the base Setup.exe file stored in the following location:<br />

178 ISE-1800-UG01 <strong>InstallShield</strong> <strong>2012</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!