Options for embedding Chromium instead of IE WebBrowser control with WPF/C#

Embedding Chromium Instead of IE WebBrowser Control with WPF/C#

📝 Updated for 2020! 🎉 Check out my article where I compare the memory footprints of different approaches to hosting HTML WebView in a basic Windows Desktop application: Comparing Process Working Sets of WebView-Based Windows Desktop Apps

If you're developing a WPF/C# project that involves HTML editing and are looking for options to embed Chromium instead of the Internet Explorer (IE) WebBrowser control, you're in the right place. The WebBrowser control has its fair share of issues, such as keyboard and focus problems and memory leaks. Luckily, there are alternative solutions available that can address these problems and provide a better experience for your users.

Here are some options you can consider:

Awesomium and Awesomium.NET

Awesomium is an option that may seem appropriate for your project. However, it's worth noting that the project is not open-source and the full source code is not easily available. Additionally, if off-screen rendering isn't a critical requirement for your project, Awesomium might be overkill.

Chromium Embedded Framework (CEF) and .NET bindings for CEF

The Chromium Embedded Framework (CEF) along with its .NET bindings is arguably the best option currently available. This project is actively maintained and is in sync with Chrome version 27. CEF3 uses Chrome's multi-process architecture, and it has received endorsement from Adobe. This option provides a robust and reliable way to embed Chromium in your WPF/C# project.

Google's Chrome Frame

Although Google has discontinued Chrome Frame, it can still be a viable option for embedding Chromium. Originally designed as an HTML5 plugin for IE and Firefox, Chrome Frame can be used as a standalone ActiveX control that can be wrapped for use with WPF. It offers a sufficient API for interacting with the inner web page. While updating it with the latest Chromium code might require some effort, it provides you with full control over the integration.

WebKit .NET Wrapper

Although not Chromium-based and lacking the V8 engine, the WebKit .NET Wrapper is not a suitable option for embedding Chromium. However, if Chromium compatibility is not a priority, it can still serve your needs.

If you think I may have missed any other options, please let me know! I would greatly appreciate it if someone could share their experience with any of the mentioned options in a real-life, production-quality WPF project. Any insights into integration, licensing, or deployment implications would be invaluable.

Don't hesitate to leave a comment below and share your thoughts or experiences. Let's discuss the best ways to embed Chromium in your WPF/C# project and make HTML editing a breeze! 💪🌐💻