4 ms·
This week I've been dealing with an IE11 related problem from a C# app. The C# app is built using WebBrowser Control[1] which is tightly integrated with the ap
by omh 5y ago
This week I've been dealing with an IE11 related problem from a C# app.
The C# app is built using WebBrowser Control[1] which is tightly integrated with the app itself.
WebBrowser only supports IE11 but the webapps that it connects to are increasingly dropping support.
The vendor is reluctant to upgrade their app because the replacement options apparently (?) require extensive refactoring to get the same integration.
IE11 seems to be in a weird limbo. But the fact that it's still technically supported by Microsoft means that conservative software vendors aren't forced to migrate.
[1] https://docs.microsoft.com/en-us/dotnet/desktop/winforms/controls/webbrowser-control-windows-forms https://docs.microsoft.com/en-us/dotnet/desktop/winforms/con...
- tester34 5y agoHow about WebView2? https://docs.microsoft.com/en-us/microsoft-edge/webview2 https://docs.microsoft.com/en-us/microsoft-edge/webview2
- omh 5y agoI've been asking the vendor the same question! They seem to think it's not a drop-in replacement and don't want to rework their code to deal with the changes. I'm not sure to what extent this is Microsoft making compatibility hard or just a lazy vendor.
- adzm 5y agoIt is a completely different API compared to WebBrowser/MSHTL. It is akin to using CEF (Chromium Embedded Framework) for the most part. This can require rewriting pretty much everything that interacts with the browser currently as well as dealing with a completely different threading and event model in the new APIs (both WebView2 and WebKit/CEF/etc)