Evergreen Webview2
If you are a developer distributing a native app (e.g., WPF or WinForms), you cannot assume the user has WebView2 installed.
| Feature | Evergreen Mode | Fixed Version Mode | | :--- | :--- | :--- | | Disk Space | Low (Shared Runtime) | High (Per-App Runtime) | | Security | Auto-updated by Microsoft | Manual updating required | | Web Standards | Always up-to-date | Frozen at specific version | | Internet Required | Yes (for install/updates) | No (can work offline) | | Best For | Consumer apps, SaaS, general tools | Kiosks, medical devices, strict enterprise envs |
For most modern software development, the Evergreen WebView2 is the superior choice. It aligns native development with the web’s "always moving forward" philosophy while minimizing maintenance overhead for the developer.
Evergreen WebView2: A Comprehensive Approach to Building Modern Web Applications
Abstract
The rapid evolution of web technologies has led to the development of innovative solutions for building modern web applications. One such solution is WebView2, a component that enables developers to embed web content within their applications. However, managing WebView2 instances can be challenging, especially when it comes to ensuring that the component remains up-to-date and secure. In this paper, we propose the concept of "Evergreen WebView2," a comprehensive approach to building modern web applications that leverages the power of WebView2 while ensuring its perpetual updating and security.
Introduction
WebView2 is a component that allows developers to embed web content within their applications, providing a seamless user experience. It is built on top of the Microsoft Edge browser and provides a range of benefits, including improved performance, enhanced security, and better compatibility with modern web standards. However, managing WebView2 instances can be challenging, especially when it comes to ensuring that the component remains up-to-date and secure.
The Challenges of WebView2 Management
Managing WebView2 instances involves several challenges, including:
The Concept of Evergreen WebView2
To address the challenges of WebView2 management, we propose the concept of "Evergreen WebView2." Evergreen WebView2 is a comprehensive approach to building modern web applications that leverages the power of WebView2 while ensuring its perpetual updating and security.
The key principles of Evergreen WebView2 are: evergreen webview2
Benefits of Evergreen WebView2
The benefits of Evergreen WebView2 include:
Implementation of Evergreen WebView2
The implementation of Evergreen WebView2 involves several steps, including:
Conclusion
In this paper, we proposed the concept of "Evergreen WebView2," a comprehensive approach to building modern web applications that leverages the power of WebView2 while ensuring its perpetual updating and security. The benefits of Evergreen WebView2 include improved security, enhanced compatibility, and increased productivity. We believe that Evergreen WebView2 has the potential to revolutionize the way we build modern web applications and look forward to exploring its applications in future research. If you are a developer distributing a native app (e
Future Work
Future work on Evergreen WebView2 includes:
References
When your app initializes an CoreWebView2Environment, the WebView2 loader looks for an available runtime:
This means that while the runtime is shared, a clean Windows machine can still run your app seamlessly—the first launch silently fetches the runtime from Microsoft’s CDN.
Shipping the Fixed Version runtime adds ~150-180 MB to your installer. The Evergreen model keeps your app lightweight—sometimes as small as 100 KB for the bootstrapper. The Concept of Evergreen WebView2 To address the
The Evergreen runtime has both 32-bit and 64-bit versions. If your app is compiled for AnyCPU, you must ensure you initialize WebView2 using the correct architecture. Use CoreWebView2Environment.GetAvailableBrowserVersionString() to detect.
| Feature | Evergreen WebView2 | Fixed Version WebView2 | | :--- | :--- | :--- | | Update cadence | Automatic, frequent (roughly every 4-6 weeks) | Developer-controlled; you ship a specific version | | Disk footprint | Shared (one copy per machine) | Per-app (each app bundles its own runtime) | | Network bandwidth | One download for all apps | Each app downloads its own copy | | Security model | Always patched | You must republish to patch | | Best for | Most line-of-business apps, public-facing apps | Air-gapped, appliance-like, or strict version control scenarios |