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>Edition</strong>: <strong>InstallShield</strong> Premier <strong>Edition</strong> and <strong>InstallShield</strong> Professional <strong>Edition</strong> enable you to create your own merge modules.<br />

Specifying the Directories that Contain Merge Modules<br />

<strong>InstallShield</strong> lets you specify the locations on your local machine, or on a network, where you are storing<br />

merge modules (.msm files). This flexibility enables you to store merge modules in source code control<br />

and to share a common set of merge modules with other team members.<br />

<strong>InstallShield</strong> offers several ways for specifying the search paths for merge modules:<br />

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

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

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

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

comma-delimited list of folders.<br />

If you use an .ini file to specify ISCmdBld.exe parameters, you can use the MergeModulePath<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 MergeModulePath<br />

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

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

an ordered array of paths.<br />

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

\MergeModules,\MyCustomMergeModules<br />

The Redistributables view lists the names of the merge modules that correspond with the merge<br />

modules that are present in the various search paths that are specified on the Merge Modules tab of the<br />

Options dialog box. If the same merge module is in multiple search paths, <strong>InstallShield</strong> shows only the<br />

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

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

setting.<br />

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

locations and includes the appropriate merge modules in your release as needed. If the same merge<br />

module is in multiple search paths, <strong>InstallShield</strong> includes in the build only the first instance that it<br />

encounters. It uses the following order to search for merge modules:<br />

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

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

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

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

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

default directories, in order:<br />

a. <strong>InstallShield</strong> Program Files Folder\System<br />

b. <strong>InstallShield</strong> Program Files Folder\Modules\i386<br />

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

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

Saved successfully!

Ooh no, something went wrong!