Edit

Extensions in the package manifest schema

  • Article

Most of the elements in the app package schema are related to defining extensions that integrate your app with the Windows 10 OS in various ways. The app package schema supports two main types of extensions:

  • Package-level extensions. These types of extensions apply to the entire package. These extensions are defined in elements that are direct descendant of the Package element.
  • Application-level extensions. These extensions apply only to a specific application that is defined in the package. These extensions are defined in elements that are direct descendant of an Application element.

The reason there are both package-level and application-level extensions is because the package schema supports multiple applications in a single package (these are sometimes called multiple-app packages). The ability to define extensions for a specific application in the package is important for some multi-app package scenarios.

Some extensions can be defined at both the package level and application level. These extensions have elements that are defined under both the Package and Application paths in the schema.

For more details about some of the most common types of package-level and application-level extensions, see Integrate with package extensions.

Package-level extensions

For reference information about the available package-level extensions, see the Category attribute and child elements of the following Extension elements that are descendants of the Package element.

Application-level extensions

For reference information about the available application-level extensions, see the Category attribute and child elements of the following Extension elements that are descendants of an Application element.