Contents
Introduction
Installation
Guides
- Engine
- Profile
- Browser
- BrowserView
- Navigation
- Content
- Context menu
- DOM
- JavaScript
- Pop-ups
- Dialogs
- Downloads
- Chrome extensions
- Network
- Cache
- Cookies
- Proxy
- Authentication
- Permissions
- Plugins
- Printing
- Passwords
- User data profiles
- Credit cards
- Media
- Zoom
- Spell checker
- Deployment
- Chromium
Troubleshooting
- Logging
- Common exceptions
- Application does not terminate
- Video does not play
- Cannot sign in to Google account
- User data is not stored
- Color scheme
- Startup failure
- Slow startup on Windows
- Unresponsive .NET Application
- Unexpected Chromium process termination
- Unexpected behavior
- Windows 7/8/8.1 end of support
Migration
System requirements
This page describes the software and hardware configurations required to run a program based on DotNetBrowser.
Software requirements
.NET
- .NET Framework 4.6.2 — 4.8.1 (Windows only)
- .NET 5 - 9
Avalonia UI
- 11.1.2 and higher
Windows
DotNetBrowser supports x86, x64, and ARM64:
- Windows 11
- Windows 10
- Windows Server 2022
- Windows Server 2019
- Windows Server 2016
Windows 7/8/8.1 and the corresponding Windows Server versions are no longer supported.
Linux
DotNetBrowser supports the following Linux distributions (x64 and ARM64):
- Ubuntu 18.04 or later
- Debian 10 or later
- Fedora Linux 38 or later
- openSUSE 15.5 or later
- RedHat Enterprise Linux 8.9 or later
Chromium does not work in the headless environment. In order to use DotNetBrowser in headless environments including Linux-based Docker containers and WSL, you need to start X server.
macOS
DotNetBrowser supports the following macOS distributions (x64 and ARM64):
- Sequoia 15
- Sonoma 14
- Ventura 13
- Monterey 12
- Big Sur 11
macOS must run in the non-headless mode, because Chromium does not support the headless mode on this platform.
Hardware requirements
HiDPI monitors
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
Android/iOS
DotNetBrowser does not support mobile devices with iOS and Android.
Other Environments
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.