EO.WebBrowser is a web browser engine based on Google's Chrome project but with native .NET programming interface --- don't worry, it's not a wrapper around the Chrome browser installed on your machine. In fact EO.WebBrowser has the whole browser engine embedded inside EO.WebBrow
Who would use EO.WebBrowser?
EO.WebBrowser is not a new browser to join the browser war. Instead EO.WebBrowser is .NET class library that contains a set of .NET components for you to easily integrate Web page related features in your own application. In another word, it's for application developers. The TabbedBrowser sample demonstrats how easy it is to create a real mini Web Browser with EO.WebBrowser. C# and Visual Basic.NET source code are supplied with the sample. However any .NET programming language can be used. It also have a C++ programming interface. If your application already uses .NET's built-in WebBrowser control, then EO.WebBrowser would be a perfect replacement.
Why use EO.WebBrowser?
Based on Google's Chrome Project
EO.WebBrowser uses the same core Google's Chrome and Apple Safari uses. It does not rely on IE. The engine is much faster and safer.
Zero External Dependency
Native .NET components written in C#
Because it's written in .NET, you can use it with any .NET based language/development tool. The same DLL works for both 32 bit and 64 bit environments;
Easy to use Programming Interface
EO.WebBrowser offers core components that can be used in any Windows application, as well as wrapper controls for both Windows Forms applications and WPF applications, and wrapper class for native C++ applications;
Extensive Customization Options
Custom Resource Handler
Want to keep an eye on everything? Or want to keep everything to yourself? We got you covered. EO.WebBrowser offers ability to intercept and modify all requests that originate from the browser engine. For example, you can automatically deny all request sent to a specific host. It also offers you the ability to implement custom protocols or custom resource handlers. For example, you can implement a custom request handler to load images from your database instead of a Web server;