Then came WebView2. Microsoft’s answer to native embedding of modern web technologies seemed perfect—until developers hit the distribution problem . Should you ship the fixed, 200MB "Fixed Version" runtime with your app? Or ask your user to download the "Bootstrapper"?
<!-- MainWindow.xaml --> <Window xmlns:wv2="clr-namespace:Microsoft.Web.WebView2.Wpf;assembly=Microsoft.Web.WebView2.Wpf"> <Grid> <wv2:WebView2 x:Name="webView" /> </Grid> </Window> evergreen webview2
In the Electron era, a user with five desktop apps had five separate Chromium runtimes on their SSD, each occupying 150MB. That’s 750MB of pure duplication. Each app had its own updater, its own crash reporting, and its own separate sandbox processes. Then came WebView2
