DotNetBrowser64 1.18.0
DotNetBrowser 1.x is no longer officially supported by TeamDev:
https://dotnetbrowser-support.teamdev.com/docs/guides/migration/v1-v2.html#how-long-will-dotnetbrowser-version-1x-be-supported
dotnet add package DotNetBrowser64 --version 1.18.0
NuGet\Install-Package DotNetBrowser64 -Version 1.18.0
<PackageReference Include="DotNetBrowser64" Version="1.18.0" />
paket add DotNetBrowser64 --version 1.18.0
#r "nuget: DotNetBrowser64, 1.18.0"
// Install DotNetBrowser64 as a Cake Addin #addin nuget:?package=DotNetBrowser64&version=1.18.0 // Install DotNetBrowser64 as a Cake Tool #tool nuget:?package=DotNetBrowser64&version=1.18.0
A Chromium-based WPF/WinForms component that can be embedded into your .NET application to display modern web pages built with HTML5, CSS3, JavaScript, Silverlight etc.
To be able to use DotNetBrowser, you should obtain a licence by filling a form at https://www.teamdev.com/dotnetbrowser#evaluate
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net is compatible. |
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|
Chromium 64-bit process support
DotNetBrowser distribution package now includes both Chromium 64-bit and 32-bit binaries.
Important: Please note that Chromium 64-bit binaries can be used only on Windows 64-bit and cannot be used on Windows 32-bit.
More information about Chromium 64-bit process support you can find here: https://dotnetbrowser.support.teamdev.com/solution/articles/9000154412-chromium-64-bit
Clear HTTP (basic) authentication cache
The API has been extended with new functionality that allows clearing HTTP Auth cache.
More information on how to use this functionality you can find here: https://dotnetbrowser.support.teamdev.com/solution/articles/9000110186-working-with-cachestorage
Fixes:
- The issue with getting an incorrect mouse position using a `WPFBrowserView` instance in the heavyweight rendering mode. For more information, see: https://dotnetbrowser.support.teamdev.com/solution/articles/9000154696-wpf-mouseeventargs-getposition-returns-incorrect-position
- The issue with crashing a `WPFBrowserView` instance in the heavyweight rendering mode during process termination.
- The issue with the form autofill.
- The issue with availability of the password manager.
Improvements:
- Improve focus transferring in `WinFormsBrowserView` in the heavyweight rendering mode.
- Improve Chromium binaries verification process during on startup.
- Improve compatibility with Visual Studio Code Analysis.
- Add possibility to delete Chromium binary files at runtime if there are no alive `Browser` or `BrowserView` instances.