InstallShield 2016 » 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.
To add one more dependencies to your App-V package:
| 1. | In the Microsoft App-V Assistant, open the Dynamic Suite Composition page. |
| 2. | To add a dependency App-V package, click the New button. The Open dialog box opens. |
| 3. | Open the directory where the dependency App-V package that you want to add is located. That application’s .osd and .sft files are listed. |
| 4. | 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. |
Note • 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 App-V package is now listed in the Dependency Applications list and, by default, the Mandatory option is selected.
| 5. | Set the status of the selected App-V package by doing one of the following: |
| • | 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. |
| 6. | Build the primary App-V package. |
Deleting a Dependency Application from the List
To remove an App-V package from the Dependency Applications list, select the application and click the Delete button.
See Also
Dynamic Suite Composition Page
InstallShield 2016 Help LibraryMay 2017 |
Copyright Information | Flexera Software |