DotNetBrowser 1.11.1

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
.NET Framework
Additional Details

DotNetBrowser 1.x is no longer officially supported by TeamDev:
https://dotnetbrowser-support.teamdev.com/docs/guides/migration/v1-v2.html#how-long-will-dotnetbrowser-version-1x-be-supported

There is a newer version of this package available.
See the version list below for details.
The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore. 
dotnet add package DotNetBrowser --version 1.11.1
NuGet\Install-Package DotNetBrowser -Version 1.11.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="DotNetBrowser" Version="1.11.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add DotNetBrowser --version 1.11.1
#r "nuget: DotNetBrowser, 1.11.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install DotNetBrowser as a Cake Addin
#addin nuget:?package=DotNetBrowser&version=1.11.1

// Install DotNetBrowser as a Cake Tool
#tool nuget:?package=DotNetBrowser&version=1.11.1

A Chromium-based WPF/WinForms component that can be embedded into your .NET application to display modern web pages built with HTML5, CSS3, JavaScript, Silverlight etc.

To be able to use DotNetBrowser, you should obtain a licence by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate

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 55.0.2883.87.

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 (dotnetbrowser-chromium.exe). JavaScript and plugins on the web page are executed in separate native processes as well. If an unexpected error happens in the web page's plugin or DOM, your application will continue working. You can listen to events about unexpected termination of Chromium process and restore the Browser component if necessary.

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 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.

WPF and WinForms Support

The browser component has two separate views, one for WPF applications and another one for WinForms. 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.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on DotNetBrowser:

Package Downloads
DotNetBrowser.Wpf The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

A Chromium-based WPF component that can be embedded into your .NET application to display modern web pages built with HTML5, CSS3, JavaScript etc. You can obtain a free 30-day trial by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate
DotNetBrowser.WinForms The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

A Chromium-based WinForms component that can be embedded into your .NET application to display modern web pages built with HTML5, CSS3, JavaScript etc. You can obtain a free 30-day trial by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on DotNetBrowser:

Repository Stars
Necrobot-Private/NecroBot
NecroBot2
Version Downloads Last updated
2.26.1 575 3/28/2024
2.26.0 1,154 2/27/2024
2.25.1 711 1/22/2024
2.25.0 2,502 12/27/2023
2.24.2 1,550 11/22/2023
2.24.1 1,522 10/20/2023
2.24.0 1,881 10/3/2023
2.23.3 1,120 9/6/2023
2.23.2 1,034 8/3/2023
2.23.1 2,202 6/22/2023
2.23.0 3,746 5/25/2023
2.22.1 830 4/27/2023
2.22.0 2,064 3/23/2023
2.21.0 2,436 2/27/2023
2.20.1 1,677 2/7/2023
2.20.0 1,334 12/28/2022
2.19.0 947 12/5/2022
2.18.0 4,537 10/21/2022
2.17.0 1,567 10/5/2022
2.16.1 2,715 8/23/2022
2.16.0 2,093 8/8/2022
2.15.1 2,395 6/17/2022
2.15.0 1,413 6/14/2022
2.14.0 3,478 4/29/2022
2.13.1 3,218 4/12/2022
2.13.0 1,415 4/7/2022
2.12.0 2,752 3/23/2022
2.11.0 9,479 1/14/2022
2.10.0 4,248 11/18/2021
2.9.0 16,232 9/24/2021
2.8.0 2,818 8/20/2021
2.7.0 1,680 7/26/2021
2.6.0 3,933 5/27/2021
2.5.0 4,105 4/7/2021
2.4.0 3,677 3/2/2021
2.3.0 7,304 11/26/2020
2.2.0 4,557 9/9/2020
2.1.1 8,061 7/2/2020
2.1.0 1,460 6/18/2020
2.0.0 6,149 2/27/2020

DotNetBrowser 1.11.1
Resolved issues:
-DownloadHandler not working if the DotNetBrowser assembly was loaded via Assembly.Load().
-Sporadic Chromium crashes for BrowserView running in the lightweight mode.
.NET memory leak in the ImageProvider implementation.
-WPFBrowserView focus stealing issue (reproducible for WPF ToolBar buttons in the same window).