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
Migrating from 2.0 to 2.1
DotNetBrowser version 2.1 brings some improvements to both internal features and public API of the library. The engine version got updated to Chromium 79. This guide shows how to make your application code written with DotNetBrowser version 2.0 compatible with version 2.1.
Why migrate?
We recommend you to update your code to the latest version because all the new features, Chromium upgrades, support of new operating systems and .NET Framework versions, bug fixes, security patches, performance, and memory usage enhancements are applied on top of the latest version.
How long does it take?
From our experience, upgrade to a new version may take from a couple of hours to a few days depending on the number of the features you use in your application. As usual, we strongly recommend to test your software after the upgrade in all the environments it supports.
Getting help
In case you did not find the answer in this guide and you need assistance with the migration, please contact us. We will be happy to help.
Key changes
Download Handler
The StartDownloadHandler
property is moved from IDownloads
to IBrowser
interface.
v2.0
engine.Downloads.StartDownloadHandler =
new Handler<StartDownloadParameters, StartDownloadResponse>((p) =>
{
return StartDownloadResponse.DownloadTo(Path.Combine(Path.GetTempPath(),
p.Download.Info.SuggestedFileName));
});
engine.Downloads.StartDownloadHandler =
New Handler(Of StartDownloadParameters, StartDownloadResponse)(Function(p)
Return StartDownloadResponse.DownloadTo(Path.Combine(Path.GetTempPath(),
p.Download.Info.SuggestedFileName))
End Function)
v2.1
browser.StartDownloadHandler =
new Handler<StartDownloadParameters, StartDownloadResponse>((p) =>
{
return StartDownloadResponse.DownloadTo(Path.Combine(Path.GetTempPath(),
p.Download.Info.SuggestedFileName));
});
browser.StartDownloadHandler =
New Handler(Of StartDownloadParameters, StartDownloadResponse)(Function(p)
Return StartDownloadResponse.DownloadTo(Path.Combine(Path.GetTempPath(),
p.Download.Info.SuggestedFileName))
End Function)
Dropped functionality
In the new version, the following functionality is no longer supported:
- The
INetwork.TransactionStarted
event. You can use theINetwork.StartTransactionHandler
instead. - The
INetwork.BytesReceived
event. You can use theINetwork.ResponseBytesReceived
event instead. - The
INetwork.BytesSent
event. - The
Url
propertty is no longer available in theCanAccessFileParameters
used byINetwork.CanAccessFileHandler
.