Updating packaging docs for runFullTrust capability and multiple appl…

…ications (#24) * Clarifying that AppSilos can't be mixed and matched with other app types, and clarified runFullTrust capability * Updating runFullTrust note * Clarifying user global state and not machine * Update docs/packaging/msix-packaging-tool.md Co-authored-by: Dylan DSilva <[email protected]> --------- Co-authored-by: Dylan DSilva <[email protected]>
microsoft · May 26, 2023 · c32f3cd · c32f3cd
1 parent f866c57
commit c32f3cd
Showing 1 changed file with 7 additions and 0 deletions.
diff --git a/docs/packaging/msix-packaging-tool.md b/docs/packaging/msix-packaging-tool.md
@@ -61,6 +61,8 @@ on the size of the package.
 
     In the manifest, the following changes will need to be made.
 
+    **Note**: Isolated win32 applications are not compatible with other application types within the same package.
+
     * Add `xmlns:previewsecurity2="http://schemas.microsoft.com/appx/manifest/preview/windows10/security/2"`
     to the `<Package>` element
 
@@ -72,6 +74,11 @@ on the size of the package.
     * In `<Application>` replace any existing entrypoint/trustlevel/runtimebehavior with
     `uap10:TrustLevel="appContainer" previewsecurity2:RuntimeBehavior="appSilo"`
 
+    * **Note**: By default MPT, will automatically add `<rescap:Capability name="runFullTrust">` to
+    `<Capabilities>` due to the app being a packaged Win32. This should be removed unless
+    the app has other manifested extensions which can affect the user global state, such as
+    `comServer` or `FirewallRules`, since those require the `runFullTrust` capability.
+
     ![image](images/11-packaging-manifest.png)
 
 3. The app might need additional capabilities to function correctly now that it has been isolated.