Download Teamdev DotnetBrowser v1.21.3 Cracked

Teamdev DotnetBrowser v1.21.3 Cracked

Teamdev DotnetBrowser v1.21.3 Cracked
Teamdev DotnetBrowser v1.21.3 Cracked

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.

The new version of DotNetBrowser introduces a number of requested features, and fixes making the library work even smoother:

Certificate chain

The CertificateVerifyParams.IntermediateCertificates property allows getting the intermediate certificate list retrieved from the server that can be used to reconstruct and verify the complete certificate chain.

Disable form autofill functionality

The BrowserContext.AutoFillEnabled property allows enabling or disabling auto-fill functionality.

jаvascript requests focus

The Browser.FocusRequested event allows getting notifications when jаvascript requests setting focus to a Browser instance.

Hide scrollbars

The --hide-scrollbars switcher allows hiding scroll bars on the web pages. It might come handy when taking an image of a webpage.


The Chromium binaries verification process now respects the modification date.

Fixed issues:

The pop-up window does not respect the passed size and location.
The NullReferenceException in SpellCheckerService and ZoomService for the second and subsequent BrowserContext instances during application runtime.
The issue with finding the full path to the DotNetBrowser.ChromiumX.dll files.
The WinFormsBrowserView component in the heavyweight rendering mode is disposed even if it is removed from the child list of the form and the form is closed.
The usage of the back and forward mouse buttons in WPFBrowserView (heavyweight rendering mode) leads to the System.InvalidCastException exception.
The offline jаvascript service workers are not initialized properly.

Only for V.I.P
Warning! You are not allowed to view this text.
Users of Guests are not allowed to comment this publication.