Patch Creation - Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

Patch Creation

Wise Package Studio Reference
Note
If you exclude a file or directory that is under a user profile, the user profile name is
replaced with a variable that always represents the current user profile name.
9. To apply the changes to this package definition file only, mark the check box at the
bottom of the page.
If you clear this check box, any changes you make on this page are saved in the
exclusions list and will affect exclusions for future package definitions.
10. To edit an exclusion, double-click it in the list.
11. Click OK on the File and Folder Exclusions page.
Use Patch Creation to create a Windows Installer patch file (.MSP) that updates installed
versions of a Windows Installer-based application. A patch file can update one or several
previous versions. Unlike full installations, a patch installation contains only the
information necessary to update an installed version of the application.
Patch Creation uses three files from the Microsoft Windows Installer SDK:
PATCHWIZ.DLL, MSPATCHC.DLL, and MAKECAB.EXE. They are installed in the Windows
Installer Editor application directory. You specify settings in Patch Creation, and it saves
those settings in a patch settings file (.PCP). Patch Creation then sends the patch
settings file to PATCHWIZ.DLL, which creates the patch file (.MSP).
Note
Patch Creation is only applicable to Windows Installer (.MSI) technology, not WiseScript
technology. For patching WiseScript installations, use the SmartPatch page in
Installation Expert in WiseScript Package Editor.
Patch Creation guidelines
Before you use Patch Creation, use UpgradeSync. UpgradeSync compares your
current package with the previous version of the package, and prepares the current
package for a patch or upgrade.
See UpgradeSync on page 138.
The package code must be different between the old installations and the updated
installation. To see the package code in Windows Installer Editor, click the Summary
icon in Setup Editor > Product tab. Changing the Version field on the Product
Details page causes the package code to be updated, as does running UpgradeSync.
The previous version or versions must have been installed using Windows Installer.
To edit an existing patch, you need access to its patch settings file (.PCP).
If other patches exist for this package, you need access to the most recent patch file
(.MSP) to read its file sequence number and disk ID.
You need access to the complete installation in .MSI format for every installation
that this patch will upgrade and for the latest version of your application. If the
installation package includes external compressed or uncompressed files, you need
them also.
Wise Package Studio Tools
128