noderet.blogg.se - Installmate 9 component contains no installation objects

#INSTALLMATE 9 COMPONENT CONTAINS NO INSTALLATION OBJECTS PLUS#

Finally, any Set Component State actions that the installer encounters may further modify the component's state.Īfter the component state is determined as documented above, the installer sets the component action based on the criteria shown in the following table.(The predefined OptionsDlg dialog box includes this control, for example.) If the the Component is visible in UI option is set (see below), then the user may change the component's state if at least one of the the installer's dialog boxes includes an OptionTree control.

If one or more $comp=state options are present on the installer's command line, then they are evaluated and may override in turn the results from the previous steps.

This may override the states determined in step 1.

If a previous version of the same product is already present on the target system, then its component states are loaded and applied to the components.

#INSTALLMATE 9 COMPONENT CONTAINS NO INSTALLATION OBJECTS PLUS#

The initial state is based on the Initial state and If condition true fields that you define for the component in your InstallMate project, plus the Platforms, Language, and Condition fields as evaluated by the installer at runtime:.The component is displayed and selected in the installer's user interface, and cannot be unselected.ĭuring installation, the installer determines the actual component's state as follows.

The component is displayed and selected in the installer's user interface.

The component is displayed in the installer's user interface, but not selected. The component is displayed in the installer's user interface, but in a disabled state and cannot be selected by the user. The component or assembly is not selected. If the component state changes to Unavailable while the control is present, the component will be shown as Disabled. Note: This only applies if the component state is set before an OptionTree control is shown. The component is unavailable and will not be displayed in the installer's user interface. The following states are available: State Component statesĮach component has an associated state that determines if the component will be installed. Note that assembly-type components are never visible in the installer's user interface. In that case the component's installation state is typically set through its Platforms, Languages, or Condition options (see below), or through an explicit Set Component State action.

If a component does not have its Component is visible in UI option checked, then the component is not presented to the user.

The user can then select or unselect the component for installation.

If a component has its Component is visible in UI option checked (see below), then it will be shown in any OptionTree control that is used in the installer's dialog pages typically this will be the predefined OptionsDlg dialog box.

Visible versus internal componentsĬomponents may be visible to the user, or they may be for internal use only. A component is installed if it's a top-level component or a descendant of one or more ancestor components that are selected for installation, subject to the component's Condition, Platforms, and Languages attributes (see below).Ĭomponents are not required any installation object (file, folder, shortcut, registry value, etc.) that is not assigned to a component is installed or removed irrespective of any platform or language considerations. Typically, a component contains one or more files, plus any related installation objects. A Component defines a group of installation objects that must be installed or removed together.