Dependencies View
AdminStudio 2025 R2 | 30.0 | Virtual Package Editor
The Dependencies view is available for App-V 4.x packages.
The Dependencies view is where you specify other App-V packages that the open App-V package requires.
Icons in the Dependencies View
The Dependencies explorer in the Dependencies view uses different icons to help you distinguish between different types of items. Following is a list of the possible icons in the Dependencies view.
| Icon | Description |
|---|---|
 | This icon identifies the root node—the Dependencies explorer. |
 | This icon identifies an App-V package (.sft) that the open App-V package (the primary App-V package) requires. |
 | This icon identifies a target in the primary App-V package. It is recommended that all of the targets in your virtual package be associated with each of the package’s dependencies. |
Settings in the Dependencies View
The settings that are displayed in the Dependencies view differ, depending on whether you select an App-V package (.sft file) or a target in this view:
.sft Settings
When you select an .sft file in the Dependencies view, the following settings are available.
| Setting | Description |
|---|---|
| Name | This read-only setting shows the name of the required .sft file. |
| GUID | This read-only setting shows the globally unique identifier (GUID) that is associated with the required App-V package. |
| SysGuard File | This read-only setting shows the folder and name of the required App-V package’s SysGuard file ( osguard.cp ). The SysGuard file describes how the virtual environment needs to be set up. |
| HREF | Enter the URL for the published location of the required App-V package on the virtual application server. Typically, this location matches the App-V server URL for the App-V package that contains the dependency. |
Target Settings
When you select a target in the Dependencies view, the following settings are available.
| Setting | Description |
|---|---|
| Name | This read-only setting shows the name of the target that is associated with the required App-V package. |
| Mandatory | Specify whether the required App-V package is mandatory in order for the primary package (the App-V package that you are editing in the Virtual Package Editor) to run properly. Note that if the dependency is mandatory, the primary package cannot run without loading the required package. |
See Also
Specifying a Virtual Package’s Dependencies
Adding a Dependency to a Virtual Package
Associating a Package’s Targets with a Dependency in a Virtual Package
Specifying Whether a Dependency is Mandatory for a Target in a Virtual Package