Packaging, deployment, and query glossary
- application user model ID
The application user model ID uniquely identifies an app on the operating system so the operating system can send notifications and so on to the app.
- block map
Defines the indices and cryptographic hashes for blocks of executable code and data that are stored in the files of an app package. A BlockMap.xml file is required for every app package.
- dependency package
A package on which another package depends. The dependency is declared in the dependent package's manifest and not in the dependency package's manifest.
- dependent package
A package that takes a dependency on another package. The dependency is declared in the dependent package's manifest.
- footprint files
Files within an app package that are not part of the app to be deployed. These files provide metadata pertaining to the package. Standard footprint files include the manifest, block map, stream map, and digital signature. Footprint files are created as part of the package build process. In addition per the OPC specification, [Content_Types].xml and files whose names match the "*\_rels\*.rels" pattern are footprint files.
An XML file that describes the contents and metadata associated with a package including the package ID. A manifest XML file is required for every app package.
Open Packaging Conventions (OPC) describes a container-file technology that is documented in the ISO/IEC 29500 and ECMA 376 standards. App packages are OPC-compliant.
The unit of deployment, management, and servicing software associated with the app packaging model. A package contains the files that constitute the app, along with a manifest file that describes the software to Windows.
- package family name
A serialized form of the package ID that uniquely represents the package family on the computer. It is suitable for naming objects such as files and folders. The package family name is similar to the package full name, but includes only the name and publisher. Because it excludes info that changes with servicing (version, architecture, and resource info), it is useful for version-independent references to the package.
- package full name
A serialized form of the package ID that uniquely represents this version of the package on the computer. It is suitable for naming objects such as files and folders.
- package ID
A globally unique identifier for a package. It is composed of a tuple of attributes for the package including name, publisher, supported architecture, resource info, and version. See package full name and package family name for serialized forms of the package ID.
- package relative application ID
The Id attribute on the Application element within the package manifest, which is also known as PRAID. This string uniquely identifies an app within a package. This attribute is required for the Application element.
- payload files
The files within an app package that are part of the app to be deployed. These files are extracted and placed in the user's installation folder.
- resource ID
An optional part of a package ID that is used to differentiate the resources in the package. For example, a resource ID can be used to specify the language or locale.
- ZIP central directory
The byte sequences in a ZIP file that store metadata about the ZIP archive and its contents including name, size, compression settings, and location within the archive.
Build date: 11/16/2013