Jan 02 2019 09:09 AM
Hello,
I'm looking for a description of load behaviour in msix packages.
Sample: Simple app loads help.txt from %programfiles%\demo
Is this correct?
thanks and kindly regards
Andreas
Jan 02 2019 11:31 AM
SolutionThanks for your question! Here is a description of what happens when you have a main package and a modification packages.
Scenario 1: Main package with help.txt in vfs with no modification packages
When the app runs, main app will load help.txt.
Scenario 2: Main package with help.txt in vfs with modification packages that contains no help.txt in vfs
When the app runs, the main app will load help.txt from the main app
Scenario 3: Main package with help.txt in vfs with modification package that contains help.txt in vfs
When the app runs, the main package will load help.txt from the main app. This is because we found that the main package will always win over the modification packages.
Scenario 4: main package does not contain help.txt in vfs with modification package that contains help.txt in vfs. This is because when we do a look up, help.txt is first found in the modification package.
When the app runs, the main app will load help.txt from the modification package
Scenario 5: main package does not contain help.txt in vfs with modification package #1 (amodi.msix) and modification package #2 (bmodi.msix), both having help.txt in vfs.
When the app runs, the main app will load help.txt from modification package #1. This is because when we do a look up, we found help.txt first in amodi.msix.
In the next update, we will be fixing scenario #3, so that modification packages can overlay their files correctly when loading the main package. More details will be posted at http://aka.ms/msix soon.
More info on modification packages in the current release visit https://docs.microsoft.com/en-us/windows/msix/modification-package-1809-update
Jan 02 2019 10:08 PM
Hi Dian,
thanks for your help - perfectly.
What is the timeframe for fixing scenario #3?
Andreas
Jan 11 2019 09:51 AM
The fix is out in our Insider Fast build. Please go ahead and test out the feature and let us know if you run into issues.
Jan 11 2019 10:43 AM
Make sure you are on 18312 or later.
Jan 12 2019 02:35 AM
I've tested with 18312 but it doesn't works. Main package always win.
Jan 14 2019 09:38 AM
To support this scenario we added a attribute in the manifest under <Properties>. Make sure your modification package has the following attribute:
<Properties>
<rescap6:ModificationPackage>true</rescap6:ModificationPackage>
</Properties>
To update the manifest follow these steps:
Documentation highlighting these changes are coming shortly.
Jan 16 2019 10:43 PM
Wow, it's great. Thanks.
Jan 17 2019 10:04 AM
Hi Dian, it works perfectly with insider build 18312, but it fails at build 1809. Is there a plan to update 1809 to ignore the attribut if exists in a manifest.
thx
Jan 17 2019 11:10 AM
Hi, does the modification package fail to install or the functionality is not working?
Jan 17 2019 01:27 PM
Jan 17 2019 01:56 PM
Can you ensure that the min version of the manifest includes 1809 build? It should be something like this:
<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0"/>
Jan 18 2019 09:48 AM
Sure. Attached is the manifest file. App install works perfectly with 18312 and 18317. When installing at 1809, the install process terminate with "Error in parsing the app package". See picture.
Jan 18 2019 09:49 AM
And here's the manifest
Jan 21 2019 08:32 AM
Hi Dian, after installing Windows SDK 10.0.18312.0 on 1809 t is possible to use the attribut and create a modification package with makeappx.exe. The package fails with the same exception.
I've seen the description to the new functionality at your web page and the hint to the january release of MSIX packaging tool. Where can i find this. Thx
Jan 22 2019 11:31 AM
Can you try installing the package using Powershell commands?
Jan 22 2019 11:53 AM
Sure, but installation fails:
-------------------------------
add-appxpackage : Fehler bei Bereitstellung. HRESULT: 0x80080204, Das Manifest des Appx-Pakets ist ungültig.
Fehler 0xC00CE014: Überprüfungsfehler bei App-Manifest: Das App-Manifest muss gemäß dem Schema gültig sein: Zeile 10,
Spalte 6. Hinweis: Das festgelegte Schema für MaxVersionTested erkennt keine XML-Felder mit dem
http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6-Namespace. Stellen Sie
sicher, dass MaxVersionTested richtig angegeben ist. Ursache: Der Inhalt des Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6}Modificat
Fehler 0xC00CE014: Überprüfungsfehler bei App-Manifest: Das App-Manifest muss gemäß dem Schema gültig sein: Zeile 10,
Spalte 6. Hinweis: Das festgelegte Schema für MaxVersionTested erkennt keine XML-Felder mit dem
http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6-Namespace. Stellen Sie
sicher, dass MaxVersionTested richtig angegeben ist. Ursache: Der Inhalt des Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6}Modificatio...' ist
gemäß dem Inhaltsmodell des übergeordneten Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Properties' nicht gültig.
HINWEIS: Wenn Sie weitere Informationen wünschen, suchen Sie im Ereignisprotokoll nach [ActivityId]
e26d322e-b1a9-0002-06ba-6fe2a9b1d401, oder verwenden Sie die Befehlszeile Get-AppxLog -ActivityID
e26d322e-b1a9-0002-06ba-6fe2a9b1d401
In Zeile:1 Zeichen:1
+ add-appxpackage .\NativeNotepadPolicySettings2.msix
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (D:\MSIX\Samples...ySettings2.msix:String) [Add-AppxPackage], Exception
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand
Jan 24 2019 08:49 AM
Hi Dian, it works. I've forgotten "IgnorableNamespaces="rescap6">" in the manifest. thx.
Jan 02 2019 11:31 AM
SolutionThanks for your question! Here is a description of what happens when you have a main package and a modification packages.
Scenario 1: Main package with help.txt in vfs with no modification packages
When the app runs, main app will load help.txt.
Scenario 2: Main package with help.txt in vfs with modification packages that contains no help.txt in vfs
When the app runs, the main app will load help.txt from the main app
Scenario 3: Main package with help.txt in vfs with modification package that contains help.txt in vfs
When the app runs, the main package will load help.txt from the main app. This is because we found that the main package will always win over the modification packages.
Scenario 4: main package does not contain help.txt in vfs with modification package that contains help.txt in vfs. This is because when we do a look up, help.txt is first found in the modification package.
When the app runs, the main app will load help.txt from the modification package
Scenario 5: main package does not contain help.txt in vfs with modification package #1 (amodi.msix) and modification package #2 (bmodi.msix), both having help.txt in vfs.
When the app runs, the main app will load help.txt from modification package #1. This is because when we do a look up, we found help.txt first in amodi.msix.
In the next update, we will be fixing scenario #3, so that modification packages can overlay their files correctly when loading the main package. More details will be posted at http://aka.ms/msix soon.
More info on modification packages in the current release visit https://docs.microsoft.com/en-us/windows/msix/modification-package-1809-update