Dynamic Suite Composition Page

InstallShield 2024 » Microsoft App-V Assistant

Edition:The Microsoft App-V Assistant is included in the Premier Edition of InstallShield.

Version:This information applies to App-V 4.x packages.

A virtual package may rely on one or more other virtual packages in order to function properly. The Microsoft App-V Assistant lets you specify other App-V packages that the open App-V package (the primary package) requires. This capability, called Dynamic Suite Composition, enables your virtual package to interact with the other virtual applications in the virtual environment. Dynamic Suite Composition enables you to deploy common system components once on each client system, making them available for use by many App-V packages, rather than requiring you to include them with each of the App-V packages that are dependent on them. This reduces redundancy in the local App-V cache and simplifies the construction and testing of the primary virtual application.

To specify App-V packages that you want to include in a dynamic suite, use the Dynamic Suite Composition page of the Microsoft App-V Assistant.

The following settings are available on the Dynamic Suite Composition page.

Dynamic Suite Composition Page

Option

Description

Dependency App-V Packages

List of all of the dependency App-V packages that have been selected for the primary App-V package.

Mandatory

Indicates whether to selected dependency App-V package is required in order for the primary App-V package to run.

•

If the dependency App-V package is mandatory—If the primary App-V package will not run unless it can locate this dependency App-V package, leave the Mandatory option selected. If a dependency App-V package that is configured as Mandatory is not available, an error will be generated when someone attempts to run the primary App-V package.

•

If the dependency App-V package is not mandatory—If the primary App-V package will run even if it cannot locate this dependency App-V package, clear the Mandatory option.

New Button

To add an App-V package to the Dependency App-V Packages list, click this button and select the App-V package (.osd, .sft) that you want to add. Select one of the following:

•

One of the .osd files—If this dependency App-V package is or is going to be published on a server, select any one of the .osd files that are listed. If these .osd files were created properly, each of them should contain the information that will identify to the primary App-V package the published location of the dependency App-V package.

It is not necessary to select more than one .osd file. All of them contain the same reference to the location of the dependency App-V package’s .sft file, which is the only reference that is necessary in order for the primary App-V package to locate it.

•

The .sft file—If this dependency App-V package is or is going to be published locally on the client or at an accessible network location, you may select just the .sft file.

The selected reference App-V package is now listed in the Dependency Applications list and, by default, the Mandatory option is selected.

Delete Button

Click to delete the selected App-V package from the list.