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
We develop a WinForms application which is based on .NET4.8 target framework. We integrate a .NET8 web application which is presented in the target application using the WebView2 control. When the user opens the application, changes then the windows scaling setting for his main monitor and opens the control with the webview2 afterwards, then our entire application seems to be frozen.
After some investigation it turned out that it is not really frozen and the underlying system reacts to user interactions. So the WinForms message loop is still working behind. Also the menus like Context menu and Main strip menus are working as expected. Even if we manage somehow to close the WebView2 control in the application then this issue disappears, but reappears when we open it again. After further investigation it turned out that it is related to the DpiAwareness of the application and the WebView2 itself. This behavior is described in the comments of the following issue. At the end the proposed solution is to use PerMonitorV2 setting for the application.
Since our application uses DpiAwareness set to System which is defined in the app.config file, we tried this and it really seems to solve the issue. After discussing this change with the platform development of the application unfortunately it turned out that using the PerMonitorV2 setting is not an option, because using this mode might cause many other issues based on their previous experiments/experience. After discussing these issues with Microsoft support it turned out that these issues won't be solved on .NET 4.8 anymore, therefore this setting can't be changed.
This seems to be a critical issue from user point of view, because everything seems to be frozen. If the application is in full-screen mode at the moment when they enter this situation then they might even think that the entire system is broken, and the only option is to kill the application or restart the machine (and losing all unsaved changes).
Importance
Important. My app's user experience is significantly compromised.
What happened?
We develop a WinForms application which is based on .NET4.8 target framework. We integrate a .NET8 web application which is presented in the target application using the WebView2 control. When the user opens the application, changes then the windows scaling setting for his main monitor and opens the control with the webview2 afterwards, then our entire application seems to be frozen.
After some investigation it turned out that it is not really frozen and the underlying system reacts to user interactions. So the WinForms message loop is still working behind. Also the menus like Context menu and Main strip menus are working as expected. Even if we manage somehow to close the WebView2 control in the application then this issue disappears, but reappears when we open it again. After further investigation it turned out that it is related to the DpiAwareness of the application and the WebView2 itself. This behavior is described in the comments of the following issue. At the end the proposed solution is to use PerMonitorV2 setting for the application.
Since our application uses DpiAwareness set to System which is defined in the app.config file, we tried this and it really seems to solve the issue. After discussing this change with the platform development of the application unfortunately it turned out that using the PerMonitorV2 setting is not an option, because using this mode might cause many other issues based on their previous experiments/experience. After discussing these issues with Microsoft support it turned out that these issues won't be solved on .NET 4.8 anymore, therefore this setting can't be changed.
This seems to be a critical issue from user point of view, because everything seems to be frozen. If the application is in full-screen mode at the moment when they enter this situation then they might even think that the entire system is broken, and the only option is to kill the application or restart the machine (and losing all unsaved changes).
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
Latest
SDK Version
Latest
Framework
Winforms
Operating System
Windows 11
OS Version
22631.5039
Repro steps
Demo app
dpifreezedemo-release.zip
Steps
Symptoms
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: