Please note: DotNetBrowser can be used only with the license. You can obtain a free 30-days evaluation licence at https://www.teamdev.com/dotnetbrowser#evaluate. DotNetBrowser is a .NET component which allows embedding a Chromium-based browser control into .NET applications to display web pages built with HTML5, CSS3, JavaScript, etc. DotNetBrowser supports WinForms .NET graphical subsystem and provides UI controls which you can embed into your .NET Desktop Application to display web pages. This package provides the WinForms UI control for the Visual Studio Toolbox. Chromium All required Chromium binaries are deployed with the library. You don't need to install Google Chrome to work with DotNetBrowser. DotNetBrowser uses Chromium build 127.0.6533.73. Rendering Everything you see on the loaded web page inside the browser is rendered by the Chromium engine. DotNetBrowser just displays web page parts rendered by the Chromium engine, which makes the web page look exactly as in Google Chrome. Multi-Process Architecture DotNetBrowser inherits Chromium's Multi-Process Architecture. Each web page is rendered in a separate native process Memory Usage Since all Chromium functionality runs in separate native processes, the Chromium engine doesn't use the memory of your .NET application. Bidirectional JavaScript to .NET Bridge DotNetBrowser supports two-way communication with a loaded web page. The component's API makes any part of the HTML document accessible from your C# or VB.NET code. Moreover, it is possible to register an event handler on particular DOM elements and be notified about the occurred events. In addition, DotNetBrowser provides the ability to execute JavaScript code on the loaded web page. This ability can be used to call any JavaScript function and obtain the result of its execution at the .NET side. It is also possible to do the opposite - the C# or VB.NET method can be called from the JavaScript code as a regular JavaScript function. WinForms Support The browser component has two separate views, one of them is for WinForms applications. It is also possible to use it without a view at all - DotNetBrowser is not required to be displayed to work properly. Each view is a control that supports a set of properties and events that are basic for the corresponding toolkit. |