Windows Installer Editor Reference
54
Setting Up
Setting Wildcard Groups
On the Wildcard Groups tab, you can create groups of wildcards so you don’t have to
type multiple wildcards repeatedly.
On the Files and Web Files pages in Installation Expert, you use the wildcard groups
when you add directory contents. Wildcard groups on the Wildcard Groups tab appear in
the Include Wildcards list on the Add Contents and Wildcard Details dialog boxes.
Select a wildcard group to add just a subset of the files in the directory whose contents
you are adding.
Several wildcard groups are predefined, which you can edit. If you delete them, they are
recreated when the application starts. Also, wildcards that you enter in any Include
Wildcards field are added to the list of wildcard groups.
Note
(Visual Studio integrated editor.) To display context-sensitive help, click the Wise Help
link on this dialog box.
To add a wildcard group so it appears in Include Wildcards
1. Select Tools menu > Options and click the Wildcard Groups tab.
In Visual Studio: Tools menu > Options> Wise Options > Wildcard Groups.
2. On the Wildcard Groups tab, click Add.
The Wildcard Group Details dialog box appears.
3. Complete the dialog box and click OK:
Group Name
Enter a name to precede the wildcards in the Include Wildcards list. This is a
visual identifier to help you quickly find the wildcards in the list.
Wildcards
Enter semi-colon delimited wildcards. (Example: Enter *.EXE;*.DLL for all .EXE
and .DLL files. A ? represents any one character.)
Later, when you add contents or set automatic updating on the Files or Web Files page,
this wildcard group is available from the Include Wildcards list.
See also:
Setting Options
on page 37
Creating and Editing Installation Templates
When you create a new installation or merge module, it gets its configuration from a
template file. Templates contain logical defaults and commonly used settings. Some
template files are predefined and appear when you create a new installation. You also
can create your own templates.
Example: If all your installations have the same system configuration requirements and
document file extensions, you can create a template with these changes preconfigured.
