This article describes how DotNetBrowser is supplied and which libraries should be deployed.
DotNetBrowser is supplied in a few dynamic libraries. Some f them are related to DotNetBrowser itself and others to the appropriate Chromium binary files.
Here's a list of the libraries provided in the distribution package:
|DotNetBrowser main DLL for any environment. Contains all the .NET-related logic including UI controls.|
|DotNetBrowser32.dll||~2 MB||DotNetBrowser.Chromium32.dll||DotNetBrowser main DLL for x86 environment. Supports x64 environment.|
|DotNetBrowser64.dll||~2 MB||DotNetBrowser.Chromium64.dll||DotNetBrowser main DLL for x64 environment. Does not support x86 environment.|
|DotNetBrowser.Chromium32.dll||~61.7 MB||Chromium x86 binaries. This DLL is a container for the bound Chromium-based engine.|
|DotNetBrowser.Chromium64.dll||~64.7 MB||Chromium x64 binaries. This DLL is a container for the bound Chromium-based engine.|
The libraries you have to deploy depend on the Windows architecture and your .NET application platform.
DotNetBrowser.dll, DotNetBrowser.Chromium32.dll and DotNetBrowser.Chromium64.dll libraries should be included in your .NET application. For the first time, DotNetBrowser will check the applications architecture and extract/use the appropriate Chromium binaries. On Windows 64-bit DotNetBrowser will extract and use Chromium 64-bit binaries. On Windows 32-bit – Chromium 32-bit binaries.
DotNetBrowser32.dll and DotNetBrowser.Chromium32.dll. If it’s a 32-bit .NET application, then Chromium 32-bit binaries will be extracted and used. Chromium 32-bit binaries work well in both Windows 32-bit and 64-bit environments.
DotNetBrowser64.dll and DotNetBrowser.Chromium64.dll. If it’s a 64-bit .NET application, then Chromium 64-bit binaries will be extracted and used. If it’s a 32-bit .NET application – an exception will be thrown.
The way to deploy the required libraries is totally up to you.