DotNetBrowser.x64
2.27.5
Prefix Reserved
See the version list below for details.
dotnet add package DotNetBrowser.x64 --version 2.27.5
NuGet\Install-Package DotNetBrowser.x64 -Version 2.27.5
<PackageReference Include="DotNetBrowser.x64" Version="2.27.5" />
paket add DotNetBrowser.x64 --version 2.27.5
#r "nuget: DotNetBrowser.x64, 2.27.5"
// Install DotNetBrowser.x64 as a Cake Addin #addin nuget:?package=DotNetBrowser.x64&version=2.27.5 // Install DotNetBrowser.x64 as a Cake Tool #tool nuget:?package=DotNetBrowser.x64&version=2.27.5
DotNetBrowser
Integrate a Chromium-based browser into your .NET application to load and process modern web pages built with HTML5, CSS3, JavaScript etc.
To be able to use DotNetBrowser, you should obtain a license. A free 30-day evaluation license can be requested by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate
Deep Chromium integration
DotNetBrowser provides API that can be used to interact with a huge set of various Chromium features directly from the code:
- DOM API: you can access Document Object Model of the loaded web page, find elements and interact with them, handle and dispatch DOM events for the particular nodes.
- JS-.NET bridge: you can execute JavaScript on the web page and process the results. You can also inject any .NET object into the web page and then use it in your JavaScript code.
- Printing API: you can initiate and configure printing programmatically. Printing to PDF is also supported out of box.
- Network API: you can intercept, redirect, handle, and suppress network requests, override HTTP headers and POST data, filter out incoming and outgoing cookies, change proxy settings on the fly.
See the examples to understand what can be implemented with DotNetBrowser.
Easy deployment
All required Chromium binaries are deployed as DotNetBrowser DLLs and can be extracted automatically during execution. You don't need to pre-install Chromium, Google Chrome, or a Chromium-based runtime to work with DotNetBrowser.
The current release of DotNetBrowser uses Chromium build 129.0.6668.59.
Headless mode
DotNetBrowser can be used in Windows services and server apps. The web page can be loaded and rendered completely in memory without displaying any visible windows. You can then take a screenshot of the loaded web page.
User input simulation
DotNetBrowser provides means to simulate mouse and keyboard input and interact with the web page programmatically - exactly as regular users do.
UI
DotNetBrowser provides UI controls for WPF and Windows Forms applications. These controls can be used to display web pages as integral parts of the .NET applications. It is also possible to use DotNetBrowser to create VSTO add-ins.
Usage
Note: The VB.NET examples can be found in the examples repository.
WPF
XAML
<Window x:Class="Sample.Wpf.MainWindow"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:wpf="clr-namespace:DotNetBrowser.Wpf;assembly=DotNetBrowser.Wpf"
mc:Ignorable="d"
Title="MainWindow" Height="450" Width="800" Closed="MainWindow_OnClosed">
<Grid>
<wpf:BrowserView x:Name="browserView"/>
</Grid>
</Window>
Code
using System;
using System.Windows
using DotNetBrowser.Browser;
using DotNetBrowser.Engine;
namespace Sample.Wpf {
public partial class MainWindow : Window {
private readonly IEngine engine;
private readonly IBrowser browser;
public MainWindow() {
InitializeComponent();
// Create and initialize the IEngine
engine = EngineFactory.Create();
// Create the IBrowser
browser = engine.CreateBrowser();
browser.Navigation.LoadUrl("https://html5test.teamdev.com/");
// Initialize the WPF BrowserView control
browserView.InitializeFrom(browser);
}
private void MainWindow_OnClosed(object sender, EventArgs e) {
browser.Dispose();
engine.Dispose();
}
}
}
Windows Forms
using System;
using System.Windows.Forms;
using DotNetBrowser.Browser;
using DotNetBrowser.Engine;
using DotNetBrowser.WinForms;
namespace Sample.WinForms {
public partial class Form1 : Form {
private readonly IEngine engine;
private readonly IBrowser browser;
public Form1() {
InitializeComponent();
// Create and initialize the IEngine
engine = EngineFactory.Create();
// Create the Windows Forms BrowserView control
BrowserView browserView = new BrowserView() {
Dock = DockStyle.Fill
};
// Create the IBrowser
browser = engine.CreateBrowser();
browser.Navigation.LoadUrl("https://html5test.teamdev.com/");
// Initialize the Windows Forms BrowserView control
browserView.InitializeFrom(browser);
// Add the BrowserView control to the Form
Controls.Add(browserView);
Closed += Form1Closed;
}
private void Form1Closed(object sender, EventArgs e) {
browser.Dispose();
engine.Dispose();
}
}
}
Avalonia UI
AXAML
<Window xmlns="https://github.com/avaloniaui"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:app="clr-namespace:DotNetBrowser.AvaloniaUi;assembly=DotNetBrowser.AvaloniaUi"
mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
x:Class="Embedding.AvaloniaUi.MainWindow"
Title="Embedding.AvaloniaUi" Closed="Window_Closed">
<app:BrowserView x:Name="BrowserView"/>
</Window>
Code
using System;
using Avalonia.Controls;
using DotNetBrowser.Browser;
using DotNetBrowser.Engine;
namespace Embedding.AvaloniaUi
{
/// <summary>
/// This example demonstrates how to embed DotNetBrowser
/// into an Avalonia application.
/// </summary>
public partial class MainWindow : Window
{
private const string Url = "https://html5test.teamdev.com/";
private readonly IBrowser browser;
private readonly IEngine engine;
public MainWindow()
{
// Create and initialize the IEngine
engine = EngineFactory.Create();
// Create the IBrowser instance.
browser = engine.CreateBrowser();
InitializeComponent();
// Initialize the Avalonia UI BrowserView control.
BrowserView.InitializeFrom(browser);
browser.Navigation.LoadUrl(Url);
}
private void Window_Closed(object? sender, EventArgs e)
{
browser?.Dispose();
engine?.Dispose();
}
}
}
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETFramework 4.5
- DotNetBrowser.Chromium.Win-x64.Net45 (>= 2.27.5)
- protobuf-net (>= 2.4.0)
-
.NETStandard 2.0
- DotNetBrowser.Chromium.Win-x64.NetStandard20 (>= 2.27.5)
- protobuf-net (>= 2.4.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on DotNetBrowser.x64:
Package | Downloads |
---|---|
UnicontaPages
UnicontaPages is dll containing Pages related code for WPF application. To use the UnicontaPages you will need your own Uniconta APP identifier. http://www.uniconta.com/en/developers/ |
|
ClientTools
ClientTools is dll containing all controls related code for Uniconta application. To use the ClientTools you will need your own Uniconta APP identifier. http://www.uniconta.com/en/developers/ |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
2.27.6 | 124 | 11/12/2024 |
2.27.5 | 235 | 10/2/2024 |
2.27.4 | 222 | 9/13/2024 |
2.27.3 | 308 | 8/5/2024 |
2.27.2 | 231 | 6/21/2024 |
2.27.1 | 195 | 5/30/2024 |
2.27.0 | 188 | 5/22/2024 |
2.26.2 | 506 | 4/24/2024 |
2.26.1 | 200 | 3/28/2024 |
2.26.0 | 290 | 2/27/2024 |
2.25.1 | 260 | 1/22/2024 |
2.25.0 | 281 | 12/27/2023 |
2.24.2 | 444 | 11/22/2023 |
2.24.1 | 2,473 | 10/20/2023 |
2.24.0 | 254 | 10/3/2023 |
2.23.3 | 316 | 9/6/2023 |
2.23.2 | 320 | 8/3/2023 |
2.23.1 | 398 | 6/22/2023 |
2.23.0 | 376 | 5/25/2023 |
2.22.1 | 398 | 4/27/2023 |
2.22.0 | 539 | 3/23/2023 |
2.21.0 | 492 | 2/27/2023 |
2.20.1 | 501 | 2/7/2023 |
2.20.0 | 691 | 12/28/2022 |
2.19.0 | 643 | 12/5/2022 |
2.18.0 | 938 | 10/21/2022 |
2.17.0 | 796 | 10/5/2022 |
2.16.1 | 894 | 8/23/2022 |
2.16.0 | 795 | 8/8/2022 |
2.15.1 | 950 | 6/17/2022 |
2.15.0 | 904 | 6/14/2022 |
2.14.0 | 1,001 | 4/29/2022 |
2.13.1 | 994 | 4/12/2022 |
2.13.0 | 1,015 | 4/7/2022 |
2.12.0 | 1,035 | 3/23/2022 |
2.11.0 | 871 | 1/14/2022 |
2.10.0 | 636 | 11/18/2021 |
2.9.0 | 676 | 9/24/2021 |
2.8.0 | 598 | 8/20/2021 |
2.7.0 | 606 | 7/26/2021 |
2.6.0 | 734 | 5/27/2021 |
2.5.0 | 612 | 4/7/2021 |
2.4.0 | 674 | 3/2/2021 |
2.3.0 | 2,619 | 11/26/2020 |
2.2.0 | 804 | 9/9/2020 |
2.1.1 | 19,897 | 7/2/2020 |
2.1.0 | 760 | 6/18/2020 |
2.0.0 | 930 | 2/27/2020 |
We've bumped Chromium to version 129.0.6668.59.
Find more about fixes and improvements in our release notes:
https://teamdev.com/dotnetbrowser/release-notes/2024/v2-27-5.html