Introduction
Installation
Guides
- Engine
- Profile
- Browser
- BrowserView
- Navigation
- Content
- Context menu
- DOM
- JavaScript
- Pop-ups
- Dialogs
- Downloads
- Network
- Cache
- Cookies
- Proxy
- Authentication
- Permissions
- Plugins
- Printing
- Passwords
- User data profiles
- Credit cards
- Media
- Zoom
- Spell checker
- Deployment
- Chromium
Troubleshoot
- Logging
- 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
Migration
System Requirements
This page describes the software and hardware configurations required to run a program based on DotNetBrowser.
Software Requirements
DotNetBrowser runs on Windows only.
Windows
DotNetBrowser supports computers running a 32-bit or 64-bit version of Windows:
- Windows 7, 8, 8.1, 10, 11
- Windows Server 2008 R2, 2012, 2012 R2, 2016, 2019, 2022
.NET implementations
The supported .NET implementations are listed below.
Core Functionality
- .NET Framework 4.5 - 4.8.
- .NET Standard 2.0 compatible implementations:
- .NET Core 2.2, 3.0, 3.1.
- .NET 5.
- .NET 6.
WinForms and WPF
- .NET Framework 4.5 - 4.8.
- .NET Core 3.0 - 3.1.
- .NET 5.
- .NET 6.
Hardware Requirements
- CPU: Intel Pentium 4 or higher with SSE3 support.
- RAM: 512 MB minimum.
- Hard Disk Space: 350 MB.
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 BrowserView controls are compatible with different DPI awareness modes. The DotNetBrowser UI controls get the DPI awareness settings from the application configuration where it’s used and configure 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
ARM Is Not Supported
DotNetBrowser does not support the ARM architecture.
Other Environments
You can try running DotNetBrowser on other platforms or versions not listed here, but we do not guarantee all DotNetBrowser functionality works properly on a system that does not meet the software and hardware requirements.
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.
Linux
Despite the fact that DotNetBrowser core functionality supports .NET Core 2.2 and is compatible with .NET Standard 2.0, Linux environments are not supported yet in DotNetBrowser.
Android/iOS
DotNetBrowser cannot be used on mobile devices with iOS and Android.