DotNetBrowser.Wpf 2.13.0

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package DotNetBrowser.Wpf --version 2.13.0                
NuGet\Install-Package DotNetBrowser.Wpf -Version 2.13.0                
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.Wpf" Version="2.13.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add DotNetBrowser.Wpf --version 2.13.0                
#r "nuget: DotNetBrowser.Wpf, 2.13.0"                
#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.Wpf as a Cake Addin
#addin nuget:?package=DotNetBrowser.Wpf&version=2.13.0

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

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

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://teamdev.com/dotnetbrowser");
             
            // 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://teamdev.com/dotnetbrowser");
             
            // 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();
        }
    }
}
Product 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 netcoreapp3.0 is compatible.  netcoreapp3.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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on DotNetBrowser.Wpf:

Package Downloads
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
3.0.0-eap.2 85 8/20/2024
3.0.0-eap.1 78 5/22/2024
2.27.6 170 11/12/2024
2.27.5 299 10/2/2024
2.27.4 189 9/13/2024
2.27.3 640 8/5/2024
2.27.2 800 6/21/2024
2.27.1 781 5/30/2024
2.27.0 241 5/22/2024
2.26.2 1,493 4/24/2024
2.26.1 387 3/28/2024
2.26.0 937 2/27/2024
2.25.1 313 1/22/2024
2.25.0 3,189 12/27/2023
2.24.2 1,177 11/22/2023
2.24.1 1,111 10/20/2023
2.24.0 2,980 10/3/2023
2.23.3 647 9/6/2023
2.23.2 500 8/3/2023
2.23.1 943 6/22/2023
2.23.0 1,627 5/25/2023
2.22.1 380 4/27/2023
2.22.0 668 3/23/2023
2.21.0 415 2/27/2023
2.20.1 547 2/7/2023
2.20.0 592 12/28/2022
2.19.0 402 12/5/2022
2.18.0 1,208 10/21/2022
2.17.0 541 10/5/2022
2.16.1 693 8/23/2022
2.16.0 1,425 8/8/2022
2.15.1 1,169 6/17/2022
2.15.0 578 6/14/2022
2.14.0 2,250 4/29/2022
2.13.1 852 4/12/2022
2.13.0 622 4/7/2022
2.12.0 706 3/23/2022
2.11.0 1,070 1/14/2022
2.10.0 1,198 11/18/2021
2.9.0 10,933 9/24/2021
2.8.0 1,517 8/20/2021
2.7.0 1,103 7/26/2021
2.6.0 3,596 5/27/2021
2.5.0 1,210 4/7/2021
2.4.0 2,423 3/2/2021
2.3.0 2,753 11/26/2020
2.2.0 1,008 9/9/2020
2.1.1 4,724 7/2/2020
2.1.0 664 6/18/2020
2.0.0 3,165 2/27/2020

The Chromium engine has been upgraded to version 100.0.4896.60.

Password manager API to handle the stored credentials.

Extended arrays and collections support.
The `IJsArray`, `IJsSet`, `IJsMap` and `IJsArrayBuffer` interfaces were added to simplify work with JavaScript collections from the .NET side.

In-process Chromium DevTools.

For the full list of fixes and improvements, see our release notes:
https://dotnetbrowser-support.teamdev.com/release-notes/2022/v2-13.html