Query on Schemas: Package versus Application Extensions

%3CLINGO-SUB%20id%3D%22lingo-sub-1929337%22%20slang%3D%22en-US%22%3EQuery%20on%20Schemas%3A%20Package%20versus%20Application%20Extensions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1929337%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20various%20manifest%20schemas%20have%20elements%20called%20%22Extensions%22%2C%20some%20of%20which%20live%20under%20the%20%22Package%22%20element%20or%20%22Application%22%20element.%26nbsp%3B%20The%20base%20foundation%20schema%20is%20augmented%20by%20a%20number%20of%20additional%20schemas%20and%20the%20foundation%20defines%20a%20references%20for%20the%20additional%20schemas%20to%20use.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20expected%20placement%20on%20some%20of%20these%20elements%20in%20the%20additional%20schemas%20is%20unclear%2C%20and%20online%20documentation%20seems%20to%20differ%20from%20the%20schemas%20(obtained%20from%20the%20packaging%20SDK).%20To%20provide%20an%20example%2C%20the%20extensions%20in%20UAP6%20are%20particularly%20troubling%20to%20me%20today.%26nbsp%3B%26nbsp%3B%3CSTRONG%3EIt%20would%20be%20helpful%20for%20Microsoft%20to%20explain%20the%20basic%20strategy%20of%20placing%20extensions%20at%20the%20application%20or%20package%20level%2C%20and%20when%20there%20is%20a%20choice%2C%20why%20someone%20would%20pick%20one%20over%20the%20other.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2083963%22%20slang%3D%22en-US%22%3ERe%3A%20Query%20on%20Schemas%3A%20Package%20versus%20Application%20Extensions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2083963%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F146612%22%20target%3D%22_blank%22%3E%40TIMOTHY%20MANGAN%3C%2FA%3E%2C%26nbsp%3B%20Thank%20you%20for%20providing%20the%20feedback.%20We%20updated%20our%20documentation%20to%20provide%20additional%20guidance%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fuwp%2Fschemas%2Fappxpackage%2Fuapmanifestschema%2Fextensions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExtensions%20in%20the%20package%20manifest%20schema%20-%20Windows%20UWP%20applications%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

The various manifest schemas have elements called "Extensions", some of which live under the "Package" element or "Application" element.  The base foundation schema is augmented by a number of additional schemas and the foundation defines a references for the additional schemas to use.

 

The expected placement on some of these elements in the additional schemas is unclear, and online documentation seems to differ from the schemas (obtained from the packaging SDK). To provide an example, the extensions in UAP6 are particularly troubling to me today.  It would be helpful for Microsoft to explain the basic strategy of placing extensions at the application or package level, and when there is a choice, why someone would pick one over the other.

1 Reply
Microsoft Verified Best Answer

Hi  @TIMOTHY MANGAN,  Thank you for providing the feedback. We updated our documentation to provide additional guidance: Extensions in the package manifest schema - Windows UWP applications | Microsoft Docs