DotNetBrowser 3.5.0

Added new initialization exceptions

New exception classes have been introduced to cover various engine initialization failure scenarios:

SandboxNotSupportedException - Thrown when Chromium can’t launch in the sandboxed mode, because, the environment doesn’t support creating processes within a new user namespace.
UserDataInUseException - Thrown when another Chromium instance is already using the same user data directory.
UserDataCreationException - Thrown when the user data directory cannot be created due to insufficient permissions or an invalid directory path.

All new exceptions inherit from EngineInitializationException, ensuring existing code continues to work while enabling type-safe exception handling.

Changes in loading PDF documents

You can now track PDF document loading with two new events:

PdfDocumentLoaded
PdfDocumentLoadFailed

Usage example:

browser.PdfDocumentLoaded += (sender, args) =>
{
    var url = args.Url;
    var frame = args.Frame;

    // This event is a good place to start PDF printing.
    frame.Print();
};

Starting with DotNetBrowser 3.5.0, FrameLoadFinished event and the Navigation.LoadUrl() task result are no longer reliable ways to wait for the PDF document to load. Use the new events instead.

Read more details in the navigation guide.