Edge Chromium might not be installed at all (I'd rather tell my customers to install it than ship and maintain the runtime package).The WebView2 Runtime is a customized copy of the Microsoft Edge binaries that is used to run your WebView2 applications.įingers crossed the following sentence basically just needs clarification to mean "Once GA is reached the Edge Stable Channel is able to be utilized as the WebView2 Runtime", though it sounds more like Instead of requiring that users install Microsoft Edge, your application may use the Evergreen WebView2 Runtime and Installer (Preview). Microsoft Edge Stable Channel may not be installed on all user machines where your application runs. The following channels are listed in order from most to least stable channel. By default, WebView2 targets the most stable channel available on the device that meets the minimum version requirement of the WebView2 SDK. There are multiple channels WebView2 that applications may use as the web platform. Agreed on the point to just go with Electron then (which offers a more mature ecosystem in the first place). I definitely would like to stay evergreen as part of the user's own Edge update mechanisms and not ship huge binaries myself. So I understand now, the issue is about a change to no longer support the only runtime provider a regular user will have in the future: The Edge stable channel.
It wastes a lot of memory if each webview potentially uses different Edge runtime. Indeed, I don't want to have different runtimes of Edge on my machine. This is the way webview works in Mac too, one doesn't ship runtime per webview app, and you can write static executables for it just fine. We should be able to target stable Edge user already has installed. If we have to ship runtime (the whole chromium) with the application, and each webview user must update their runtime manually, it defeats the purpose of webview. The fixed version distribution mode does not receive any automatic updates, and you should plan to manually apply updates. The fixed version distribution mode allows you to control which version of the WebView2 Runtime is used by your application, and when user machines are updated. The fixed version distribution mode allows you to select and package a specific version of the WebView2 Runtime.
"The fixed version distribution mode allows you to select and package a specific version of the WebView2 Runtime."ĭo you want to package the runtime with your app? It means you need to ship the runtime with your app, and you are responsible for updating it:įor constrained environments, there are plans to support a fixed version (previously named bring-your-own) distribution mode.
0 kommentar(er)
