SOLVED

Shared package container

%3CLINGO-SUB%20id%3D%22lingo-sub-2277460%22%20slang%3D%22en-US%22%3EShared%20package%20container%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2277460%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20to%20see%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fmanage%2Fshared-package-container%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMSIX%20Shared%20Package%20Container%20-%20MSIX%20%7C%20Microsoft%20Docs%3C%2FA%3E%26nbsp%3Bfinally%20seeing%20some%20light%20(for%20those%20that%20don't%20know%2C%20it%20is%20in%20a%20new%20insider%20preview%20build%20for%20the%20OS%20at%20this%20time).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20some%20questions%20that%20I%20don't%20think%20are%20covered%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EWhat%20about%20including%20packages%20that%20reference%20dependency%20packages%20(such%20as%20frameworks%20or%20runtimes).%26nbsp%3B%20Are%20these%20automatically%20included%20in%20the%20list%20or%20must%20they%20be%20specified%3F%26nbsp%3B%20If%20automatic%2C%20then%20what%20order%20is%20used%20for%20the%20priority%20layering%20in%20the%20list%3F%26nbsp%3B%20I'm%20not%20sure%20the%20order%20is%20terribly%20important%20for%20these%2C%20but%20we'd%20want%20to%20know%20for%20any%20troubleshooting.%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3ESince%20I'm%20asking%2C%20let's%20also%20cover%20Modification%20Packages.%26nbsp%3B%20Should%20these%20be%20listed%2C%20or%20if%20previously%20applied%20on%20the%20system%20to%20the%20primary%20package%20does%20that%20automatically%20come%20into%20the%20list%3F%26nbsp%3B%20If%20automatic%2C%20please%20confirm%20if%20this%20will%20be%20a%20priority%20just%20above%20that%20primary%20package%20it%20was%20added%20to.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2279484%22%20slang%3D%22en-US%22%3ERe%3A%20Shared%20package%20container%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2279484%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F149589%22%20target%3D%22_blank%22%3E%40Tim%20Mangan%3C%2FA%3E%2C%26nbsp%3BThanks%20for%20posting%20the%20question.%20Only%20the%20main%20package%20will%20need%20to%20be%20included%20in%20the%20shared%20package%20container%20.xml%20definition.%20In%20terms%20of%20framework%20packages%2C%20those%20will%20automatically%20be%20included.%20By%20their%20nature%2C%20modification%20packages%20and%20even%20optional%20packages%20are%20already%20launched%20via%20the%20main%20package's%20container%20so%20they%20too%20will%20not%20need%20to%20be%20specified.%20We%20will%20update%20the%20documentation%20accordingly%20to%20make%20it%20clearer.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

Great to see MSIX Shared Package Container - MSIX | Microsoft Docs finally seeing some light (for those that don't know, it is in a new insider preview build for the OS at this time).

 

I have some questions that I don't think are covered:

  • What about including packages that reference dependency packages (such as frameworks or runtimes).  Are these automatically included in the list or must they be specified?  If automatic, then what order is used for the priority layering in the list?  I'm not sure the order is terribly important for these, but we'd want to know for any troubleshooting.
  • Since I'm asking, let's also cover Modification Packages.  Should these be listed, or if previously applied on the system to the primary package does that automatically come into the list?  If automatic, please confirm if this will be a priority just above that primary package it was added to.
1 Reply
best response confirmed by TIMOTHY MANGAN (MVP)
Solution

Hi @Tim Mangan, Thanks for posting the question. Only the main package will need to be included in the shared package container .xml definition. In terms of framework packages, those will automatically be included. By their nature, modification packages and even optional packages are already launched via the main package's container so they too will not need to be specified. We will update the documentation accordingly to make it clearer.