Forum Discussion

Tim Mangan's avatar
Tim Mangan
MVP
Jan 28, 2019
Solved

MSIX: Modification Package Layering still a problem in 18317

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...
  • Dian Hartono's avatar
    Dian Hartono
    Jan 31, 2019

    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.
     

Dian Hartono's avatar
Dian Hartono
Icon for Microsoft rankMicrosoft
Jan 31, 2019

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.
 

Tim Mangan's avatar
Tim Mangan
MVP
Jan 31, 2019

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?

Resources