Package (Windows 10)
Defines the root element of an app package manifest. The manifest describes the structure and capabilities of the software to the system.
<Package IgnorableNamespaces? = A string between 1 and 32767 characters in length with a non-whitespace character at its beginning and end. > <!-- Child elements --> ( Identity & mp:PhoneIdentity? & Properties & Resources & Dependencies & Capabilities? & Extensions? & Applications? ) </Package>
? optional (zero or one)
& interleave connector (may occur in any order)
Attributes and Elements
|Attribute||Description||Data type||Required||Default value|
Declares namespaces used in the manifest that should be ignored. Ignored namespace elements are not validated and should be considered untrusted. Multiple namespaces are specified with a space between each namespace.
|A string between 1 and 32767 characters in length with a non-whitespace character at its beginning and end.||No|
Represents one or more apps that comprise the package.
Declares the access to protected user resources that the package requires.
Declares other packages that a package depends on to complete its software.
|Extensions (type: CT_PackageExtensions)||
Defines one or more extensibility points for the package.
Defines a globally unique identifier for a package. A package identity is represented as a tuple of attributes of the package.
Defines additional metadata about the package including attributes that describe how the package appears to users.
Note You may get an error if the manifest elements DisplayName or Description contain characters disallowed by the Windows firewall; namely “|” and “all”, due to which Windows fails to create the AppContainer profile for the package . Use this reference for troubleshooting if you get an error.
Declares languages for the resources that the package contains. Every package must declare at least one language for resources. The scale and DirectX feature level attributes are common for all resources in the package.
If your app is an update to an app previously made available on Windows Phone, ensure that this element matches what is in the app manifest of your previous app. Use the same GUIDs that were assigned to the app by the Store. This ensures that users of your app who are upgrading to Windows 10 will receive your new app as an update, and not as a duplicate.
This outermost (document) element may not be contained by any other elements.