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.

Build Location<br />

In the Build Location area, you can configure the following settings.<br />

Table 24-73: Build Location Settings<br />

Property Description<br />

Build Location Specify where you want your patch file built or browse for an existing folder.<br />

Chapter 24: View Reference<br />

QuickPatch Projects<br />

Create Update.exe Specify whether you want to create an Update.exe update launcher for the current<br />

QuickPatch package.<br />

To learn when an Update.exe update launcher is required, see Patching<br />

Considerations.<br />

List of Patch GUIDs to<br />

replace<br />

Create new<br />

“UpgradedImage” folder<br />

Generate<br />

MsiPatchOldAssembly<br />

tables<br />

Create patch sequencing<br />

entry<br />

To replace one or more earlier installed patches with the current QuickPatch, set this<br />

property to the patch GUIDs of those patches, and separate each with a comma. For<br />

example:<br />

{C86838C9-DEDC-4451-B96F-94AFB9460F15},{C8633E5B-AC44-45d8-B487-<br />

C68B3B1F60D6}<br />

Setting this property is typically not required, even if you have several QuickPatch<br />

projects in the History. However, if your QuickPatch project does not overwrite files<br />

added in an earlier QuickPatch project, it may be necessary to set this property.<br />

If you do not know the GUID of a patch that you want to replace, click this property and<br />

then click the ellipsis button (...). Select the patch (.msp or .exe file), and <strong>InstallShield</strong><br />

will add the corresponding GUID to this property.<br />

This setting enables you to build your QuickPatch package with an existing<br />

UpgradedImage folder. To use this option, you must have built this package at least<br />

once (so that an UpgradedImage folder exists). Setting this option to No builds the<br />

package from the existing UpgradedImage folder. This lets you tweak the .msi package<br />

in the UpgradedImage folder and use that .msi data in a QuickPatch project. Setting this<br />

option to Yes (the default setting) regenerates the .msi file in the UpgradedImage folder<br />

every time that the package is built.<br />

Specify whether to automatically generate entries for the MsiPatchOldAssemblyFile<br />

and MsiPatchOldAssemblyName tables, which allow a patch package that is running<br />

under Windows Installer 3.0 and later to patch an assembly in the global assembly<br />

cache (GAC) without making a run-time request for the original installation source. For<br />

more information, see Patching Assemblies in the Global Assembly Cache.<br />

Specify whether you want to use patch sequencing for your QuickPatch. A patch<br />

sequence accounts for obsolete patches, superseded patches, and patches that have<br />

already been applied to the product. The sequence specifies the order that Windows<br />

Installer version 3.0 and later should apply patches to an installed product, regardless<br />

of the order in which they are provided to the target machine. For versions of Windows<br />

Installer earlier than version 3.0, the patch sequence is ignored, and any patches are<br />

applied to the product in the order that they are provided to the target machine.<br />

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

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

Saved successfully!

Ooh no, something went wrong!