EO.WebBrowser for .NET 2018.2.53.0
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 a single .NET DLL. In another word, it has zero external dependency. Just reference and use.
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
What if user updates/uninstall their browser? What if user disables jР°vascript in Internet Explorer’s settings dialog? These questions does not exist with EO.WebBrowser because everything is embedded inside our DLL files.
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;
Extensive Customization Options
EO.WebBrowser offers extensive customization options that allow you to customize context menu, hot keys, jР°vascript dialogs, file dialogs, focus and window control. Together these features allow you to seamlessly integrate the browser engine into your application;
.NET code -> jР°vascript code
Turn any web page into an integral part of your application — both visually and programmatically. You can execute jР°vascript code and access all the jР°vascript objects directly from your .NET code. Access their properties or even call a jР°vascript function are all different options available to you;
jР°vascript code -> .NET code
Things always go both ways — and this is reflected in our programming interface as well. You can call jР°vascript code from .NET code, and the other way around is also true — you can call .NET code from your jР°vascript code. This allows your Web page to seamlessly interact with the host application;
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;
EO.WebBrowser Fixed calling WebView.EvaScript inside NewWindow event handler may cause browser engine to hang issue; Fixed EO.Wpf.WebControl throws exception when the object is being finalized by garage collector issue;
WebBrowser, browser, jР°vascript, engine, Chrome, inside, application, offers, Google, custom, embedded, around, interface, based, everything, programming, wrapper, applications, options, components, WebBrowser, browser, jР°vascript, engine, Chrome, inside, application, offers, Google’s, around, embedded, wrapper, interface, based, everything, programming, custom, options, applications, components