7. dubna 2012 9:11
Can someone explain a few things about using <PackageDependency> in the appxmanifest for me?
- What types of dependencies are allowed? C++ Dynamic Library DLLs? Do they need to be "Metro Style" to work? Or do they have to be WinRT Components?
- What is the Name attribute of PackageDependency? Is it an assembly namespace? A file name? With or without extensions?
- What is the schema of the Name attribute of PackageDependency? Underscores seem to not be allowed.
- How does a C# "Any CPU" app package deal with PackageDependency when there are x64, x86, and ARM versions of the C++ DLL?
- How do a add my DLL dependency to my csproj? A "copy if newer" Content file? Or do I need to add it at all?
There is very little information out there on this and no examples of it in use. Thanks for anything you can tell me!
- Upravený Tom Spilman 7. dubna 2012 9:11
11. dubna 2012 0:40Moderátor
PackageDependencies refer to other app packages that the current package depends on. Good examples are Microsoft.WinJS and Microsoft.VCLibs packages. This isn't used for other assemblies included within your own app package. It is used to refer to other packages pre-installed on the system.
The name is the name of the dependent package. An "Any CPU" package dependency will look for the appropriate CPU version: the full package identity includes the processor architecture.
- Označen jako odpověď Tom Spilman 11. dubna 2012 1:10
11. dubna 2012 1:10
From the docs in LoadPackagedLibrary it is not clear that PackageDependency is not required for loading a regular DLL that is already packaged in your app as "Content".