TeamDev DotNetBrowser v1.20.1 - Integrate a Chromium-based browser with your .NET app to display and process HTML5, CSS3, JavaScript, Flash

TeamDev DotNetBrowser v1.20.1

TeamDev DotNetBrowser v1.20.1
TeamDev DotNetBrowser v1.20.1

Integrate a Chromium-based browser with your .NET app to display and process HTML5, CSS3, jаvascript, Flash etc. DotNetBrowser provides .NET WPF / WinForms Control that can be embedded into .NET Applications to display HTML content including modern web pages. Web page is rendered by Chromium engine. Because of this web pages will look exactly as in Google Chrome.

HTML5, CSS3, jаvascript Support
DotNetBrowser supports all the modern web standards including HTML5, CSS3 and jаvascript. In general it supports the same web standards as Google Chrome™.

Multi-Process Architecture
DotNetBrowser inherits Chromium Multi-Process Architecture. It means that every web page is rendered in separate Chromium Render process. Actually all native functionality is running in separate native processes. It means that Chromium will not use memory of your .NET application.

Browser Events Listeners
You can listen to different web browser events such as start loading frame, finish loading frame, fail loading frame, document loaded in main frame, title and status change events etc.

jаvascript Dialogs Handler
The jаvascript dialogs such as alert, confirmation, prompt, beforeunload, file upload dialog can be handled using DialogHandler. You can choose whether a jаvascript dialog should be displayed or not and what the dialog should look like.

Load Handler
With LoadHandler you can handle any load activity including filtering all URLs loaded in Browser component.

Resource Handler
With ResourceHandler you can handle process of loading resources such as HTML, images, jаvascript, etc.

Save Web Page
The Browser.SaveWebPage() allows you to save the loaded web page as a set of files.

Bidirectional jаvascript to .NET Bridge
You can execute jаvascript code on the loaded web page and return the result of execution to the .NET side. You can register new jаvascript functions and associate them with .NET methods. Every time jаvascript invokes this function an appropriate .NET method will be applied.

Popups Handler
All popup windows can be handled with PopupHandler. You decide whether popup window should be displayed or not and how exactly it should be displayed (e.g. in a separate window, in your application tab etc.).

Console Listener
Using the ConsoleMessageEvent you can listen to console messages with different levels such as DEBUG, LOG, WARNING or ERROR, to get notifications about jаvascript errors on the loaded web page.

HTML5 Desktop Notifications
NotificationHandler allows you to tackle the situation when web page wants to display desktop notifications. You decide whether the web page is allowed to display notifications or not.

DOM Access
DOM API provides functionality that can be used for accessing and modifying DOM, finding particular nodes, modifying their attributes and contents, listening to DOM events and even more – all without the need to use jаvascript.

DotNetBrowser 1.20.1: Improvements and Fixes

Version 1.20.1 features several important improvements adding up to the library's convenience and productivity:

Now you can easily check if the binaries use proprietary codecs with the new ChromiumBinaries.IsCodecEnabled property.
It got simple to look the Chromium version up – just check the Product version property of assemblies.
Use DotNetBrowser conveniently with toolbox support for Visual Studio 2019.
The new dispose logic allows the instance not to wait until all separated threads are released after invoking Browser.Dispose() or BrowserView.Dispose() methods.
We have also improved the algorithm for unpacking the Chromium binaries.

Fixed Issues:

The deadlock when calling the Browser.IsDisposed() method using the WPFBrowserView instance in the lightweight rendering mode.
The InvalidCastException occurring when setting the nullable CSharp property from jаvascript side using JS - .NET Bridge API.
The rendering issue with DPI if the monitor is changed using lightweight rendering mode.
The crash which occurs if NetworkDelegate is configured and the Browser.LoadURL() method is called frequently.
The crash which occurs if a jаvascript function is invoked when the jаvascript context is invalid.

Only for V.I.P
Warning! You are not allowed to view this text.

Users of Guests are not allowed to comment this publication.