Creating A Universal Transform - Symantec WINDOWS INSTALLER EDITOR 8.0 Reference

Hide thumbs Also See for WINDOWS INSTALLER EDITOR 8.0:
Table of Contents

Advertisement

Creating a Universal Transform

Windows Installer Editor Reference
Match Upgrade Code
Mark this if the upgrade code of the transform must match the upgrade code of
the base .MSI.
Version Matching
The version of the installation (set on the Product Details page) is in the form
AA.BB.CCCC.DDDD, where AA represents the major version, BB represents the
minor version, CCCC represents the update version, and DDDD represents the
build version. Select an item in the list to have the version of the transform
checked against the version of the base .MSI. If the versions do not match, an
error is generated during installation.
Version Relationship
If you chose to check versions, specify what version relationship must be true in
order not to generate an error.
Normally, a transform is based on a specific .MSI and can change that base .MSI only.
However, in some circumstances you might want to apply the same change to multiple
.MSIs. (Example: to add a registry key that holds the company name.) To do so without
creating multiple transforms, you can create a universal transform containing limited
changes that can be applied to any .MSI.
A universal transform is based on schema.msi (a blank installation database) instead of
a specific .MSI. You do not create or assign features in a universal transform. Instead,
everything you add to a universal transform is added to a top-level, hidden feature.
You cannot make complex changes to installations with a universal transform (example:
adding files). Therefore, only a limited set of Installation Expert pages are available in a
universal transform. However, if you import the universal transform to the Software
Manager database, distribute it to the share point directory, and then open it in Windows
Installer Editor from the repository, then all the Installation Expert pages appear. This
happens because, when you apply the transform to an .MSI or a blank database during
the import, the copy in the repository is no longer a "universal" transform.
GUIDs added to item names
When you add the following items to a universal transform, a GUID is appended to the
item name:
Path variables
Resources
Environment variables
Registry entries
Properties
Shortcuts
You can see these GUIDs in the MSI tables. You cannot remove the GUIDs from the
names.
To create a universal transform
1.
Select File menu > New. The New Installation File dialog box appears.
a.
From the Categories list, select Other Templates.
b.
In the Templates/Tools list, select the Universal Transform icon and then
click OK.
Merge Modules and Transforms
344

Advertisement

Table of Contents
loading

Table of Contents