Dependency files in the software distribution are applications that are necessary for a Win32 application to function. Examples include framework packages and libraries. Although you upload them like a file and you can view them in the List View, they have reduced features.
Dependency File Features
- Dependency file does not have assignments of their own. The applications to which they are associated give the dependency files their assignments.
- Every dependency file is a separate file and the system does not create versions for the file.
- The system cannot parse information from dependency files so you must enter details such as uninstallation processes.
- Dependency files have reduced options on the Deployment Options tab.
- You cannot associate patches or transforms to dependency files.
- You can view the dependency files by setting the filters as Windows Desktop apps and Dependencies.
- If you modify the application manifest to add or remove the application dependencies, the software distribution agent installs or uninstalls the dependencies. Currently, the application must first be uninstalled and then reinstalled for the changes to take effect. If the reinstalled application is User Installed, it becomes Managed, and it is removed upon unenrollment.
Before you delete a dependency, ensure that other applications are not associate to it. When you delete the dependency file, the system removes its association from all applications. Devices newly assigned to the application do not get the dependency. Deletion does not remove the dependency from devices that had the application previous to deletion.