You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Referencing Microsoft.Web.WebView2 produces significant bloat in the output folder. The same goes for deployed app. All in all, 1 MB which can be throw away. But how?
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
1.0.2792.45
SDK Version
No response
Framework
WPF
Operating System
Windows 10
OS Version
No response
Repro steps
Create a WPF project targeting .NET 8.
Add a reference to WebView2 as shown below.
Optionally add an x64 configuration and select it.
What happened?
Referencing
Microsoft.Web.WebView2
produces significant bloat in the output folder. The same goes for deployed app. All in all, 1 MB which can be throw away. But how?Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
1.0.2792.45
SDK Version
No response
Framework
WPF
Operating System
Windows 10
OS Version
No response
Repro steps
.NET 8
.WebView2
as shown below.x64
configuration and select it.Now look in the build folder. Why do we see all this bloat? Targeting WPF and x64 we certainly don't need all this:
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: