Note: Advice in this article will only work for DotNetBrowser 1.
See the corresponding article for DotNetBrowser 2 here.
Since 1.18, DotNetBrowser distribution package includes Chromium 64-bit binaries. So, now DotNetBrowser provides the DotNetBrowser.Chromium32.dll and DotNetBrowser.Chromium64.dll libraries that contain Chromium 32-bit and Chromium 64-bit binaries accordingly.
Important: Please note that Chromium 64-bit binaries, supports only Windows 64-bit environment and cannot be used on Windows 32-bit.
Which one is used?
It depends on the Windows architecture and your .NET application platform.
Platform target:
- AnyCPU
DotNetBrowser.dll, DotNetBrowser.Chromium32.dll and DotNetBrowser.Chromium64.dll libraries should be included into 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.
- x86
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.
- x64
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.
Recommendations
If you know that your end users use only the Windows 64-bit environment or Windows 32-bit isn’t supported by your software, then it’s recommended to use only DotNetBrowser64.dll and DotNetBrowser.Chromium64.dll libraries.
If your software supports only 32-bit, then it’s recommended to use only DotNetBrowser32.dll and DotNetBrowser.Chromium32.dll.
If your software supports both Windows 32-bit and 64-bit environments, then you can use DotNetBrowser.dll, DotNetBrowser.Chromium32.dll and DotNetBrowser.Chromium64.dll libraries.
Also, DotNetBrowser is distributed via packages:
- NuGet:
- AnyCPU - DotNetBrowser
- x86 - DotNetBrowser32
- x64 - DotNetBrowser64
- VSIX:
- AnyCPU - DotNetBrowser.Package
- x86 - DotNetBrowser.Package32
- x64 - DotNetBrowser.Package64
Note: Since 1.18, DotNetBrowser creates an additional folder for unpacking binaries. The name depends on the application's platform. For platforms on x86 - "32bit" and on x64 -"64bit".