The Dependencies tab can be used to configure the dependencies of a package. It covers both, the platform related dependencies and the package related dependencies. It is divided into three different parts.
Base Application
In the Base application section of the tab, select the application for which the package will be used. Select the package by either typing the name or click on the Browse [...] button located next to the Name field and selecting the application. The publisher of the application can be entered into the Publisher field.
Target Platforms
In the Target platforms section of the tab, the supported platforms can be configured. A new platform can be added by using the + button. The entry for a platform consists of three different dropdown elements.
•Name: The Name dropdown menu can be used to select the target platform.
•Lowest supported version: The Lowest supported version dropdown can be used to select the lowest version of the platform.
•Highest tested version: The Highest tested version dropdown can be used to select the highest version of the platform. The available versions vary depending on the selected platform.
Package Dependencies
In the Package dependencies section of the tab, packages on which the package depends on can be selected. In order to add a new package to the list, click on the + button.
•Name: The field contains the name of the package that is the dependency. The packages can be selected by clicking on the Browse [...] button and selecting the target package.
•Publisher: This describes the publisher. The format fits the regular expression of a distinguished name.
•Lowest supported version: This represents the lowest version of the package that has been selected as dependency that is supported. The version string needs to be in quad notation (Major.Minor.Build.Revision).
•Highest tested major version: This represents the highest version of the dependency package that is known to be supported. The version string needs to be in quad notation (Major.Minor.Build.Revision).
•Is optional: Check this box if the dependency is only optional. If the box is not checked, the dependency is mandatory.
Driver Dependencies
In the Driver dependencies section of the tab, drivers on which the package depends on can be selected. In order to add a new driver to the list, click on the + button.
•Name: The field contains the name of the driver that is the dependency.
•Lowest supported version: This describes the lowest supported version of the driver.
•Lowest date driver package: This describes the oldest date for the driver package that is supported.
Host Runtime Dependency
In the Host Runtime Dependency section of the tab, a dependency on a host app for the current app can be defined.
•Name: The field contains the name of the host app.
•Publisher: The field contains the name of the publisher of the host app.
•Minimum version host app: This field contains the minimum version of the host app.