Deployment

This article describes what is included in DotNetBrowser distribution package and libraries to be deployed.

ZIP distribution archive

DotNetBrowser is supplied in a few dynamic libraries. Some of them are related to DotNetBrowser itself and others to the appropriate Chromium binary files.

Here’s a list of the libraries provided in DotNetBrowser distribution package:

Assembly Size References Description
DotNetBrowser.dll ~150 KB   Data classes and interfaces
DotNetBrowser.Core.dll ~1,5 MB DotNetBrowser.dll DotNetBrowser.Logging.dll Core implementation
DotNetBrowser.Logging.dll ~12 KB   DotNetBrowser Logging API implementation
DotNetBrowser.Chromium.Win-x86.dll ~65 MB   Chromium binaries for Windows 32-bit
DotNetBrowser.Chromium.Win-x64.dll ~68 MB   Chromium binaries for Windows 64-bit
DotNetBrowser.Wpf.dll ~116 KB DotNetBrowser.dll DotNetBrowser.Core.dll Classes and interfaces for embedding into a WPF app
DotNetBrowser.WinForms.dll ~107 KB DotNetBrowser.dll DotNetBrowser.Core.dll Classes and interfaces for embedding into a WinForms app


The libraries you have to deploy depend on your Windows architecture and .NET application platform.

AnyCPU
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll, DotNetBrowser.Chromium.Win-x86.dll and DotNetBrowser.Chromium.Win-x64.dll libraries must be included in your .NET application. For the first time, DotNetBrowser checks the applications architecture and extracts or uses the appropriate Chromium binaries. On Windows 64-bit, DotNetBrowser extracts and uses Chromium 64-bit binaries. On Windows 32-bit these are Chromium 32-bit binaries.

x86
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll and DotNetBrowser.Chromium.Win-x86.dll. If it’s a 32-bit .NET application, Chromium 32-bit binaries will be extracted and used. Chromium 32-bit binaries are supported for both Windows 32-bit and 64-bit environments.

x64
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll and DotNetBrowser.Chromium.Win-x64.dll. If it’s a 64-bit .NET application, Chromium 64-bit binaries will be extracted and used. If it’s a 32-bit .NET application, an exception is thrown.

DotNetBrowser.Wpf.dll or DotNetBrowser.WinForms.dll is added depending on your .NET applications framework.

As a user, you can choose the way to deploy the required libraries.

NuGet

DotNetBrowser is available as a NuGet package. You can install it using the Visual Studio NuGet Package Manager. Right-click “References” in your project, select “Manage NuGet packages…” and search for DotNetBrowser package. When the package is found, click “Install” to begin the installation.

Here is the list of the NuGet packages available:

Package References Description
DotNetBrowser DotNetBrowser.Chromium.Win-x64 DotNetBrowser.Chromium.Win-x86 Core functionality
DotNetBrowser.x64 DotNetBrowser.Chromium.Win-x64  
DotNetBrowser.x86 DotNetBrowser.Chromium.Win-x86  
DotNetBrowser.Chromium.Win-x64   Chromium binaries for Windows 64-bit
DotNetBrowser.Chromium.Win-x86   Chromium binaries for Windows 32-bit
DotNetBrowser.WinForms DotNetBrowser Control for embedding into a WinForms app
DotNetBrowser.WinForms.x64 DotNetBrowser.x64  
DotNetBrowser.WinForms.x86 DotNetBrowser.x86  
DotNetBrowser.Wpf DotNetBrowser Control for embedding into a WPF app
DotNetBrowser.Wpf.x64 DotNetBrowser.x64  
DotNetBrowser.Wpf.x86 DotNetBrowser.x86  

VSIX

If you want to add the DotNetBrowser controls to the Visual Studio Toolbox, the most convenient way is to download and install the VSIX package that is available at Visual Studio gallery.

The following packages are available:

  • DotNetBrowser.WinForms
  • DotNetBrowser.WinForms.x64.Package
  • DotNetBrowser.WinForms.x86.Package
Go Top