Package Dependencies Tab
This feature enables you to declare other packages marked as framework packages that the main package functionality depends on.
Although you may be tempted to say that the dependencies for an MSIX are similar to the prerequisite for an MSI, this is not true.
When you declare a dependency, basically you inform the Windows that your application relies on another application which also needs to be of MSIX. When the user installs your app, the OS checks its dependencies and in case one is missing then the Windows will install the related dependency.
Please keep in mind that the dependency will only be installed if the application is
installed from the Store and its dependency is al also available in the Store.
In case of a sideloading, when the application is not from the Store, the Windows will not install the dependency, instead it will just inform that a dependency is required. This is more like a launch condition.
Adding a package from the development machine as dependency
Use the toolbar button, context menu item or
press the + key. The Select an MSIX Based
product Dialog dialog will be shown, allowing you to browse for a dependency
package. You can either choose a package installed on the machine or select a package from
the disk.
Declaring a new package dependency
Use the toolbar button, context menu item or press
the Insert key. The Edit Package Dependency Dialog will be shown, allowing you to configure
and add a new package dependency.
Editing an existing package dependency
Select a package dependency in the list and use the
toolbar button, context menu item or press the
Space key. The Edit Package Dependency Dialog will be shown, allowing you to edit an existing package dependency.
Removing an existing package dependency
Select a
package dependency in the list and use the toolbar button, context
menu item or press the Delete key to remove it.
Topics
- Edit Package Dependency
Edit or create a new dependency on another package.