Table of Contents
Advertisement
Component Rules
Windows Installer Editor Reference
4.
In the Templates list, select an icon on which to base the new template. Some
icons are not templates, but instead invoke an import process or prompt to create a
new transform.
To create a template in .WSI or .WSM format, select a project icon (name ends
with "Project").
To create a template in .MSI or .MSM format, select a file icon (name ends with
"File").
5.
Click Open.
A new installation or merge module opens.
6.
Make all the changes that should appear in installations created with this template.
7.
Save the file:
a.
Select File menu > Save As.
b.
Name the file, and save it in either:
Templates\Project directory (.WSI or .WSM). These templates appear when
you select File menu > New > Project.
Templates\File directory (.MSI, .MSM, or .WSI). These templates appear
when you select File menu > New > File.
When you save the template, a page view is created with the same name and is
listed in the Page Views drop-down list. However, when you use the template to
create an installation, the default page view is the page view that was displayed
when the template was created. If the template's default page view is a custom
page view, you can customize it.
See
Customizing Page Views
8.
To test the new template, do the following:
If you saved the template in the Templates\Project directory, select File menu >
New > Project. On the New Project dialog box, click Wise Setup and Deployment
Projects in the Project Types list. Your new template should appear in the
Templates list.
If you saved the template in the Templates\File directory, select File menu >
New > File. On the New File dialog box, click Wise Files in the Categories list.
Your new template should appear in the Templates list.
9.
Select the template you just created and click OK.
10. Verify that the changes you made in the template are present in this new
installation.
You can select or create rules that help you manage the creation of components in an
installation. Using component rules eliminates the need to specify component
information for every individual resource you add to an installation and ensures that
components are created consistently across all installations. Component rules can also
help you align component GUIDs in an upgrade with component GUIDs in previous
versions of the installation.
When you first create an installation, you select a component rule set to manage
components you add to that installation. Then, whenever you add a resource, such as a
on page 23.
Setting Up
51
Advertisement
Table of Contents
Troubleshooting
