TeamDev DotNetBrowser v1.19 Retail
TeamDev DotNetBrowser v1.19 Retail
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.
SSL Certificate Dialogs
DotNetBrowser API allows handling SSL X.509 Client Certificates.
Modify User Agent
With DotNetBrowser you can modify browser’s User-Agent string that will be sent to a web server.
HTML to Image
Take a screenshot, and even capture an image of the complete web page.
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.
Geolocation and Google API support
Use Google Maps™ Geolocation API and work with Google Maps.
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.
The new version of DotNetBrowser got more flexible and stable due to the following changes:
Browser.Dispose(bool checkBeforeUnload) Implemented
Due to this method it got possible to invoke the DialogHandler.onbeforeunload method which is fired if the web page contains the onbeforeunload jаvascript event. Read more.
FileChooserParams.Filter Introduced
This property provides a meaningful description of the file extensions accepted by the file chooser. This information comes from the accept attribute of the input HTML element with the type=file attribute.
Improvements:
Now DotNetBrowser is able of managing download process even if the Browser instance which initiated the download activity has been disposed.
Starting with this update you can set the specific bitmap scaling mode for a WPFBrowserView instance in the lightweight rendering mode.
We also improved the memory usage in the Chromium binaries verification functionality.
Fixed issues:
The NullReferenceException exception which is thrown when disposing the WinFormsBrowserView instance in the heavyweight rendering mode.
The ArgumentOutOfRangeException exception which is thrown when setting the CultureInfo.
Inability to use a custom client certificate if it already exists in the certificate storage.
The UnauthorizedAccessException exception which is thrown if the LoggerProvider.Instance.OutputFile property is set to a path which has no write access.
The OutOfMemoryException exception which is thrown during verification of the Chromium binaries.
Inability to navigate with the arrow keys inside a drop-down list in the lightweight rendering mode.
The CertificateVerifyParams.VerifyFlags property always returning null.
The issue with the relative path in the BrowserContextParams constructor.
Browser.Dispose(bool checkBeforeUnload) Implemented
Due to this method it got possible to invoke the DialogHandler.onbeforeunload method which is fired if the web page contains the onbeforeunload jаvascript event. Read more.
FileChooserParams.Filter Introduced
This property provides a meaningful description of the file extensions accepted by the file chooser. This information comes from the accept attribute of the input HTML element with the type=file attribute.
Improvements:
Now DotNetBrowser is able of managing download process even if the Browser instance which initiated the download activity has been disposed.
Starting with this update you can set the specific bitmap scaling mode for a WPFBrowserView instance in the lightweight rendering mode.
We also improved the memory usage in the Chromium binaries verification functionality.
Fixed issues:
The NullReferenceException exception which is thrown when disposing the WinFormsBrowserView instance in the heavyweight rendering mode.
The ArgumentOutOfRangeException exception which is thrown when setting the CultureInfo.
Inability to use a custom client certificate if it already exists in the certificate storage.
The UnauthorizedAccessException exception which is thrown if the LoggerProvider.Instance.OutputFile property is set to a path which has no write access.
The OutOfMemoryException exception which is thrown during verification of the Chromium binaries.
Inability to navigate with the arrow keys inside a drop-down list in the lightweight rendering mode.
The CertificateVerifyParams.VerifyFlags property always returning null.
The issue with the relative path in the BrowserContextParams constructor.
Only for V.I.P Warning! You are not allowed to view this text.