Deployment

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:

Windows 

AnyCPU
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll, DotNetBrowser.Chromium.Win-x86.dll, DotNetBrowser.Chromium.Win-x64.dll, DotNetBrowser.Chromium.Win-arm64.dll and protobuf-net.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, DotNetBrowser.Chromium.Win-x86.dll and protobuf-net.dll. If it is 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, DotNetBrowser.Chromium.Win-x64.dll and protobuf-net.dll. If it is a 64-bit .NET application, Chromium 64-bit binaries will be extracted and used. If it is a 32-bit .NET application, an exception is thrown.

ARM64
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll, DotNetBrowser.Chromium.Win-arm64.dll and protobuf-net.dll. If it is an ARM64 .NET application, Chromium ARM64 binaries will be extracted and used.

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

Linux 

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

ARM64
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll, DotNetBrowser.Chromium.Linux-arm64.dll and protobuf-net.dll. If it is an ARM64 .NET application, Chromium ARM64 binaries will be extracted and used. If it is an ARM .NET application, an exception is thrown.

DotNetBrowser.AvaloniaUi.dll is added if your application uses Avalonia UI.

macOS 

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

ARM64
DotNetBrowser.dll, DotNetBrowser.Core.dll, DotNetBrowser.Logging.dll, DotNetBrowser.Chromium.macOS-arm64.dll and protobuf-net.dll. If it is an ARM64 .NET application, Chromium ARM64 binaries will be extracted and used. If it is an ARM .NET application, an exception is thrown.

DotNetBrowser.AvaloniaUi.dll is added if your application uses Avalonia UI.

Citrix 

DotNetBrowser can be used in Citrix environment with Windows Server 2016 and higher.

To run Chromium and DotNetBrowser, it’s required to disable Citrix API Hooks.

The API hooks should be disabled for chromium.exe file located in Chromium binaries directory.