One File Per Component Rule Set - Symantec WINDOWS INSTALLER EDITOR 8.0 Reference

One File Per Component Rule Set

Windows Installer Editor Reference
Group non-keypath resources by resource type
If the added resource cannot be set to the keypath, that is, if it is not a file, registry
key, or ODBC data source, add the resource to an existing component that contains
the same type of resource.
Create new components for resources not matching other criteria
For all other resources that do not match the criteria above, create a new
component for the resource and set the component key to the table name of the
keypath or the first resource. If multiple components are named for the same table,
an incremental number is added to the component name. Example, File1, File2, and
so on.
See also:
Component Rules on page 49
When you use this predefined rule set, each file you add to the installation becomes its
own component.
If an added resource does not meet the conditions in a rule, the next rule is evaluated
for that resource. If the resource does not meet the conditions in any of the rules, the
component is created according to the final rule.
Match components in previous versions of the .MSI
If the keypath resource matches a resource in the previous .MSI list, match the
component layout of the previous .MSI and set the component key to match the
previous version.
Add all files to their own components
If the added resource is a file, create a new component.
Put registry keys associated with files or components in matching
components
If the added resource is a registry key, and the registry value name or value refers
to a file or component, add the resource to an existing component that contains the
same type of resource.
Put Current User registry keys in their own component
If the added resource is a registry key under HKEY_CURRENT_USER, add the
resource to the component matching the conditions and set the component key
base to CurrentUser. The component key base will be incremented for each new
component matching this condition. Example: CurrentUser1, CurrentUser2, and so
on.
Put non-Current user registry keys in their own component
If the added resource is a registry key NOT under HKEY_CURRENT_USER, add the
resource to an existing component that contains the same type of resource.
Name new non-advertised shortcuts by destination directory
If the added resource is a shortcut, add it to an existing component containing non-
advertised shortcuts in the same destination directory.
Group non-keypath resources by resource type
If the added resource cannot be set to the keypath, that is, if it is not a file, registry
key, or ODBC data source, add the resource to an existing component that contains
the same type of resource.
Setting Up
57