msiexpert created the topic: Organization in Installanywhere
The Organization task enables developers to arrange Install Sets, Product Features,
Components, and Merge Modules. Install Sets and Features allow for levels of
installation options for the end-user of the installer. Components are the smallest
widget that can be selected by a Feature set. Install Sets are groupings of Features, and
are an organizational tool for the developer of the installer. Components may be much
more than files, they can be sophisticated actions that are required to install and run
applications or features properly.
There is an interaction between the Install Sets, Features, and Components
subtasks, as well as the Install task. If an install set is added in the Install Sets
subtask, features can be assigned to that install set in the Features subtask. If a
feature is added in the Features subtask, components can be assigned to that feature
in the Components subtask. If a component is added in the Components subtask,
files and/or actions can be assigned to that component after the files and/or actions
are added in the Install task.
Install Sets are a set of product features. The Install Sets subtask allows developers
to add, name, remove, or order Install sets in the installer. In the Install Set List,
developers define which install set (or sets) to use as the default option to provide to
the end-user. Features are assigned to install sets in the Features subtask.
When the installer requests install set information, each install set is represented by a
graphic element. The Choose Image button enables developers to select the graphic
Rules may be associated with an install set, and that association is created by selecting
Rules in the customizer and adding rules. The rules for install sets are evaluated
before the install set is installed. If the rules on the Install Set evaluate to false, the
Install Set will not be displayed.
Features are meant to identify distinct parts of the product so the end-user may
choose whether or not to install them. InstallAnywhere Product Features are
groupings of components. It is up to the developer to define the logical grouping of
components into features by assigning components to the features in the
The Features subtask enables developers to add, name, remove, or order features.
Rules may be associated with a feature set, and that association is created by selecting
Rules in the customizer and adding rules. The rules for feature sets are evaluated
before the feature set is installed. If the rules on the Feature evaluate to false, the
Feature will not be displayed.
Components are the smallest unit of organization when creating an installer. Unlike
Features and Install Sets, Components may be versioned. Components are uniquely
identified so developers may update a specific component or use the Find Component
in Registry action to locate a particular component.
The Key File is a file that must be present in all subsequent versions of the component.
The Key File is used to define the components location when the Find Component in
Registry action is used.
The Components subtask enables developers to add, name, remove, order, identify,
and version components.
Rules may be associated with component sets, and that association is created by
selecting Rules in the customizer and adding rules. The rules for component sets are
evaluated before the component set is installed.
The Modules subtask imports Merge Modules into an InstallAnywhere project.
Merge Modules are created as a build output option in the Build task.
The DIM References subtask supports referencing Developer Installation Manifests
(DIMs) in installation projects. DIMs are XML files that describe specific product
subsystems and their requirements. Application developers create DIMs using
InstallShield Collaboration, a plug-in module for Eclipse and Microsoft Visual Studio
.NET. See Referencing Developer Installation Manifests (DIMs) for more information
on referencing DIMs in your installation project.