3 ms·
I'd like to know more about why the .NET WebBrowser control was deemed unworkable. Is the problem with the actual WebBrowser control provided by the IE engine,
by mwcampbell 11y ago
I'd like to know more about why the .NET WebBrowser control was deemed unworkable. Is the problem with the actual WebBrowser control provided by the IE engine, or just the .NET interface to it (presumably the one provided by WPF)?
- myoon 11y agoThe WPF browser control is pretty weak. You don't have great control over which rendering engine it will use (default is to go to IE 7 mode!) except via writing a registry key to switch it. It provides almost no bridge between the JS and native code as well. I haven't used CefSharp, but I have used Awesomium, which provided pretty good JS-C# bindings, so I assume CefSharp has at least working JS-C# bindings.
- m_fayer 11y agoI've also had a great experience with awesomium which imo has a more powerful api than cefsharp, I'm curious why they chose it over awesomium.
- julionc 11y agoI guess the reason is that they (Awesomium) don't provide an Open Source license like MIT or GPL. Instead Github Team choose CefSharp.
- softawre 11y agoMy key problem, working with it, is you're stuck with whatever IE the user has installed on their machine. With CEF (which I've used, as have many other big companies - search your Windows PC for the dlls if you don't believe me), you're guaranteed every user has the same version of Chromium.