SOLVED

MSIX: Modification Package Layering still a problem in 18317

%3CLINGO-SUB%20id%3D%22lingo-sub-326825%22%20slang%3D%22en-US%22%3EMSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-326825%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22text-align%3A%20justify%3B%22%3EI%20used%201.2019.110%20to%20package%20and%20build%2018317%20to%20test.%20Confirmed%20the%20modification%20package%20has%20the%20%22rescap6%22%20syntax%20for%20modification%20packages.%26nbsp%3B%20Still%20doesn't%20work.%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20justify%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20justify%3B%22%3ESituation%20summary%3A%3C%2FP%3E%0A%3CUL%20style%3D%22list-style-position%3A%20inside%3B%22%3E%0A%3CLI%20style%3D%22text-align%3A%20justify%3B%22%3EMain%20app%20has%20a%20%22plugins%22%20folder%20with%203%20dlls.%3C%2FLI%3E%0A%3CLI%20style%3D%22text-align%3A%20justify%3B%22%3EModification%20package%20has%20same%20plugins%20folder%20with%20one%20NEW%20dll.%3C%2FLI%3E%0A%3CLI%20style%3D%22text-align%3A%20justify%3B%22%3ENo%20local%20folders%20matching%20where%20the%20application%20was%20%22installed%22%3C%2FLI%3E%0A%3CLI%20style%3D%22text-align%3A%20justify%3B%22%3EApp%20doesn't%20see%20the%20new%20plugin%20on%2018317%2C%20only%20the%20original%203.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EI%20created%20a%20feedback%20item%20with%20the%20same%20title%20as%20the%20subject%20on%20this%20post.%26nbsp%3B%20Attached%20both%20packages%20and%20a%20procmon%20trace%20showing%20it%20didn't%20enumerate%20the%20plugins%20folder%20of%20the%20modification%20package.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-332241%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332241%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20feedback.%26nbsp%3B%20We%20are%20working%20on%20an%20update%20and%20should%20have%20it%20for%20the%20April%20release%20(which%20will%20align%20more%20to%20the%201903%20OS%20changes).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-330247%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-330247%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EThis%20also%20fixed%20the%20problem%20for%20me%20as%20well.%26nbsp%3B%20But%20I%20repackaged%20my%20Modification%20package%20with%20the%20new%20tool%20on%20an%20insider%20machine%20with%20build%2018323.%20But%20even%20there%20I%20had%20to%20manually%20change%20the%20number.%20It%20would%20have%20been%20great%20if%20the%20Packaging%20Tool%20would%20have%20done%20that%20for%20me.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328840%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328840%22%20slang%3D%22en-US%22%3E%3CP%3EUh%2C%20OK%20if%20that%20resolves%20it.%20The%20package%20wasn't%20generated%20on%2018317%2C%20but%20with%20a%20version%20of%20the%20MPT%20that%20supports%20generating%20the%20correct%20syntax%20(if%20we%20ignore%20MaxVersionTested%20for%20a%20moment).%26nbsp%3B%20I%20can%20live%20with%20that%20now%20that%20I%20know%20to%20use%20the%20full%20features%20of%20MPT%201.2019.1%20I%20need%20to%20package%20on%2018317%20or%20above%20also.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBut%20why%20should%20%22MaxVersionTested%22%20prevent%20fixes%20in%20the%20VFS%20layering%20runtime%20from%20being%20used%3C%2FSTRONG%3E%3F%26nbsp%3B%20Surely%20we%20won't%20have%20to%20repackage%20to%20get%20the%20use%20of%20fixes%20in%20the%20runtime%20going%20forward%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328822%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328822%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20we%20looked%20at%20your%20package%20and%20noticed%20the%20MaxVersionTested%20is%20set%20to%20value%20that%20is%20early%20version%20of%20Windows.%3C%2FP%3E%0A%3CP%3EChange%20this%2C%3CBR%20%2F%3E%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.17701.0%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.17763.0%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3CBR%20%2F%3Eto%20this%2C%3CBR%20%2F%3E%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.17701.0%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.18317.1%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3CBR%20%2F%3EIt%20works.%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328128%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Modification%20Package%20Layering%20still%20a%20problem%20in%2018317%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328128%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20sending%20feedback.%20We%20are%20taking%20a%20look%20at%20the%20issue%20now.%20We%20will%20update%20the%20thread%20when%20we%20have%20an%20update.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

I used 1.2019.110 to package and build 18317 to test. Confirmed the modification package has the "rescap6" syntax for modification packages.  Still doesn't work.

 

Situation summary:

  • Main app has a "plugins" folder with 3 dlls.
  • Modification package has same plugins folder with one NEW dll.
  • No local folders matching where the application was "installed"
  • App doesn't see the new plugin on 18317, only the original 3.

I created a feedback item with the same title as the subject on this post.  Attached both packages and a procmon trace showing it didn't enumerate the plugins folder of the modification package.

 

5 Replies

Thank you for sending feedback. We are taking a look at the issue now. We will update the thread when we have an update. 

best response confirmed by John Vintzel (Microsoft)
Solution

Hi, we looked at your package and noticed the MaxVersionTested is set to value that is early version of Windows.

Change this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.17763.0" />
to this,
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17701.0" MaxVersionTested="10.0.18317.1" />
It works.
 

Uh, OK if that resolves it. The package wasn't generated on 18317, but with a version of the MPT that supports generating the correct syntax (if we ignore MaxVersionTested for a moment).  I can live with that now that I know to use the full features of MPT 1.2019.1 I need to package on 18317 or above also. 

 

But why should "MaxVersionTested" prevent fixes in the VFS layering runtime from being used?  Surely we won't have to repackage to get the use of fixes in the runtime going forward?

This also fixed the problem for me as well.  But I repackaged my Modification package with the new tool on an insider machine with build 18323. But even there I had to manually change the number. It would have been great if the Packaging Tool would have done that for me.

Great feedback.  We are working on an update and should have it for the April release (which will align more to the 1903 OS changes).

 

John.