- Context menu
- User data profiles
- Credit cards
- Spell checker
- Common exceptions
- Application does not terminate
- Video does not play
- Cannot sign in to Google acccount
- Color scheme
- Startup failure on Windows
- Slow startup on Windows
- Unresponsive .NET Application
- Unexpected Chromium process termination
- Unexpected behavior
This page describes the software and hardware configurations required to run a program based on DotNetBrowser.
- .NET Framework 4.5 — 4.8 (Windows only)
- .NET Core 2.2 (core functionality only)
- .NET Core 3.0, 3.1
- .NET 5
- .NET 6
DotNetBrowser supports both Windows 32-bit and 64-bit:
- Windows 11
- Windows 10
- Windows 8.1
- Windows 8
- Windows 7
- Windows Server 2022
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2
DotNetBrowser supports the following Linux distributions, 64-bit only:
- Ubuntu 18.04+
- Debian 10+
- Fedora Linux 33+
- openSUSE 15.2+
- RedHat Enterprise Linux 7
DotNetBrowser supports 64-bit macOS (Intel only):
- macOS 10.15+
DotNetBrowser recognizes the device scale factor that is used in the environments with HiDPI displays and renders HTML content with the respect to that scale factor.
The WPF and WinForms
BrowserView controls are compatible with different DPI awareness modes. DotNetBrowser gets the DPI awareness settings from the application configuration where it is used and configures Chromium processes to use the same DPI awareness mode.
DotNetBrowser supports high DPI only if your .NET desktop application supports it.
These MSDN articles describe how to create DPI-aware .NET desktop applications:
- High DPI desktop application development on Windows
- Creating a DPI-Aware Application
- Developing a Per-Monitor DPI-Aware WPF Application
- High DPI support in Windows Forms
Support of the ARM64 architecture for Windows, Linux, and macOS is on our Roadmap.
DotNetBrowser does not support mobile devices with iOS and Android.
You can try running DotNetBrowser on other platforms or versions not listed here, but we do not guarantee that all DotNetBrowser functionality will work properly there.
DotNetBrowser cannot be used in the environments that prevent the User32/GDI32 APIs from being called, such as Azure App Services or Azure Functions. With these limitations, it is not possible to launch the Chromium engine.