When your app initializes an CoreWebView2Environment , the WebView2 loader looks for an available runtime:
: Since the runtime is shared across all applications using the Evergreen mode, it saves significant disk space compared to the "Fixed Version" mode, which requires a dedicated copy for every app Microsoft Learn Hard-linking
: Use the Performance Best Practices Guide from Microsoft to optimize startup times and memory usage, such as sharing environments across multiple WebView2 instances. Evergreen webView2 runtime compatability issue? #2210 evergreen webview2
If you're deploying your application as an MSIX package, you can specify the WebView2 Runtime as a dependency to have it installed alongside your application. This approach handles all prerequisite logic automatically and provides a seamless installation experience.
Larger installer size; you are responsible for shipping security patches and updates. 2. The Evergreen Model When your app initializes an CoreWebView2Environment , the
Your app assumes the latest runtime. If Microsoft pushes a breaking change (e.g., deprecating a Web API), your app might break before you can update. However, this is extremely rare in practice.
In Evergreen distribution mode, the WebView2 Runtime isn't packaged with your application. Instead, it's initially installed onto clients using either an online bootstrapper or an offline installer, after which the runtime is automatically updated on client machines. This model allows you to distribute updates of your WebView2 app that use the latest WebView2 APIs from the latest SDK, without managing the runtime version yourself. The Evergreen Model Your app assumes the latest runtime
By not bundling the runtime with your application, your installer size is significantly smaller. Instead of packaging a
