Webview2: Evergreen

Developers can use the latest JavaScript features (ES6+), CSS Grid, WebAssembly, and modern web APIs without worrying about broken rendering or deprecated standards. If it works in Microsoft Edge, it works in your WebView2 app. 3. Reduced Application Size

In the , the WebView2 Runtime is not packaged with your application . Instead, it exists as a shared, system-wide component that is initially installed on client machines using either an online bootstrapper or an offline standalone installer. Once installed, the Evergreen Runtime is automatically updated on client machines in the background by Microsoft's update services. This is the distribution method that Microsoft recommends for most developers.

: While the runtime updates automatically, a running application will keep using the version it started with. To apply updates without a full app restart, you can use the NewBrowserVersionAvailable event to notify users or refresh your web environment Forward Compatibility : Test your application against Edge preview channels evergreen webview2

public async Task InitializeWebView()

The Evergreen WebView2 is Microsoft’s solution for embedding web technologies (HTML, CSS, JavaScript) into native desktop applications (WinForms, WPF, WinUI, C++). Unlike the fixed-version model, the "Evergreen" runtime automatically stays up-to-date on the user’s machine, similar to Chrome’s auto-update mechanism. Developers can use the latest JavaScript features (ES6+),

The days of shipping 200MB of browser DLLs with your app are over. The days of worrying about your users running IE11 inside your LOB app are over. The is here, quietly running on over a billion Windows devices, waiting for your next great hybrid application.

: WebView2 instances share browser, network, and GPU processes, which optimizes system resources. Reduced Application Size In the , the WebView2

A crucial nuance of the Evergreen distribution mode is how applications interact with updates. Although the runtime updates are downloaded and installed automatically by Microsoft, an already-running WebView2 application will continue to use its current loaded version of the runtime binaries until the application is restarted. This can lead to a situation where a newly installed security patch is not active until a user manually closes and reopens the application.