From 3a298d2f3178b5c6b293eb7d06b59119bfbf4e81 Mon Sep 17 00:00:00 2001 From: Michael Hoffman Date: Tue, 5 Dec 2023 08:15:24 -0800 Subject: [PATCH 1/4] Revise article --- .../webview2/concepts/distribution.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md index fb9c06f125..a69560453f 100644 --- a/microsoft-edge/webview2/concepts/distribution.md +++ b/microsoft-edge/webview2/concepts/distribution.md @@ -6,7 +6,7 @@ ms.author: msedgedevrel ms.topic: conceptual ms.prod: microsoft-edge ms.technology: webview -ms.date: 08/21/2023 +ms.date: 12/05/2023 --- # Distribute your app and the WebView2 Runtime @@ -248,6 +248,7 @@ If you have an offline deployment scenario, where app deployment has to work ent MicrosoftEdgeWebView2RuntimeInstaller{X64/X86/ARM64}.exe /silent /install ``` + #### Test your app for forward-compatibility The Web is constantly evolving. In the Evergreen distribution mode, the WebView2 Runtime is automatically kept up to date on the client to provide the latest features and security fixes. If you use Evergreen distribution, to ensure that your WebView2 app stays compatible with the web, you should set up testing infrastructure. @@ -329,11 +330,7 @@ To use the Fixed Version distribution mode: Verify that the `bin\**designated architecture**\Release` folder has a matching FixedRuntime\\(version number) folder with the runtime files in it. -#### Known issues for Fixed Version - -* Currently, Fixed Version cannot be run from a network location or UNC path. - -* Installing the Fixed Version of the WebView2 Runtime on the client causes [Microsoft PlayReady](https://www.microsoft.com/playready) to stop working. Fix the PlayReady setup as follows: +1. Starting with Fixed Version 120, unpackaged Win32 application developers using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to the security improvement in v120 to run the Renderer process inside the App Container. This doesn't impact the older runtime. Packaged apps aren't affected by this change. 1. Locate the path where you deploy the Fixed Version package on the user's device, such as the following location: @@ -348,13 +345,16 @@ To use the Fixed Version distribution mode: icacls {Fixed Version path} /grant *S-1-15-2-1:(OI)(CI)(RX) ``` - PlayReady should be working now on the user's device. - - 1. To confirm that PlayReady is installed correctly, in the **Security** tab of the **Fixed Version** folder, make sure permissions are granted for `ALL APPLICATION PACKAGES` and `ALL RESTRICTED APPLICATION PACKAGES`, as shown below: + 1. Confirm that permissions are granted for `ALL APPLICATION PACKAGES` and `ALL RESTRICTED APPLICATION PACKAGES` in the **Security** tab of the **Fixed Version** folder, as shown below: ![Permission for PlayReady](./distribution-images/play-ready-permission.png) +#### Known issues for Fixed Version + +* Currently, Fixed Version cannot be run from a network location or UNC path. + + ## Files to ship with the app From 81a06f1781d8a977e4a8cc761123b3432f33015e Mon Sep 17 00:00:00 2001 From: Michael Hoffman Date: Wed, 6 Dec 2023 09:46:01 -0800 Subject: [PATCH 2/4] on Win10 --- microsoft-edge/webview2/concepts/distribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md index a69560453f..ba17fa4b90 100644 --- a/microsoft-edge/webview2/concepts/distribution.md +++ b/microsoft-edge/webview2/concepts/distribution.md @@ -330,7 +330,7 @@ To use the Fixed Version distribution mode: Verify that the `bin\**designated architecture**\Release` folder has a matching FixedRuntime\\(version number) folder with the runtime files in it. -1. Starting with Fixed Version 120, unpackaged Win32 application developers using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to the security improvement in v120 to run the Renderer process inside the App Container. This doesn't impact the older runtime. Packaged apps aren't affected by this change. +1. On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to the security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11, the older runtime, or packaged apps. 1. Locate the path where you deploy the Fixed Version package on the user's device, such as the following location: From 27ca7b366067b758252fa5f36427dc31d0ded89d Mon Sep 17 00:00:00 2001 From: Michael Hoffman Date: Wed, 6 Dec 2023 09:53:00 -0800 Subject: [PATCH 3/4] a sec. improvement --- microsoft-edge/webview2/concepts/distribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md index ba17fa4b90..5e0e0df794 100644 --- a/microsoft-edge/webview2/concepts/distribution.md +++ b/microsoft-edge/webview2/concepts/distribution.md @@ -330,7 +330,7 @@ To use the Fixed Version distribution mode: Verify that the `bin\**designated architecture**\Release` folder has a matching FixedRuntime\\(version number) folder with the runtime files in it. -1. On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to the security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11, the older runtime, or packaged apps. +1. On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to a security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11, the older runtime, or packaged apps. 1. Locate the path where you deploy the Fixed Version package on the user's device, such as the following location: From 8d4219b977bb0892c2d9e172f1fa65d50c6d3e29 Mon Sep 17 00:00:00 2001 From: Michael Hoffman Date: Wed, 6 Dec 2023 10:03:29 -0800 Subject: [PATCH 4/4] devices --- microsoft-edge/webview2/concepts/distribution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsoft-edge/webview2/concepts/distribution.md b/microsoft-edge/webview2/concepts/distribution.md index 5e0e0df794..2b5a2940c0 100644 --- a/microsoft-edge/webview2/concepts/distribution.md +++ b/microsoft-edge/webview2/concepts/distribution.md @@ -330,7 +330,7 @@ To use the Fixed Version distribution mode: Verify that the `bin\**designated architecture**\Release` folder has a matching FixedRuntime\\(version number) folder with the runtime files in it. -1. On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to a security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11, the older runtime, or packaged apps. +1. On Windows 10 devices, starting with Fixed Version 120, developers of unpackaged Win32 applications using Fixed Version are required to run the following commands, for Fixed Version to continue to work. This is due to a security improvement in v120 to run the Renderer process inside the App Container. This change doesn't affect Windows 11 devices, the older runtime, or packaged apps. 1. Locate the path where you deploy the Fixed Version package on the user's device, such as the following location: