[🚀 Feature]: [dotnet] Road to be AOT friendly

Feature and motivation

Any consumer of Selenium library in .NET cannot use it within publishing his application as Native AOT Deployment.

The detailed affected parts are coming...

Selenium Manager ✅ v4.26

Selenium Manager - [dotnet] Json serializer gen context for SM output #14481

W3C WebDriver ✅ v4.26

New Session
... - [dotnet] Make classic WebDriver commands/responses AOT compatible #14574

W3C BiDi ✅ v4.28

... [dotnet] [bidi] Use JsonSerializerContext to be AOT friendly #15162

~~CDP (DevTools)~~

Generate JsonSerializerContext for all DTO models - [dotnet] Make DevTools area AOT compatible (breaking change) #18271
...

Fine tuning

Address all analyzer warnings
...

Usage example

Create console app, publish as native AOT, it fails at runtime.

@nvborisenko

@nvborisenko, thank you for creating this issue. We will troubleshoot it as soon as we can.

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

Blocked by bazel-contrib/rules_dotnet#443

I’m interested in this feature for running Selenium. Often times, the roads to AOT compatibility leads to improvements across the board, even for non-AOT scenarios.

Blocked by bazelbuild/rules_dotnet#443

when it will be fixed

Blocked by bazel-contrib/rules_dotnet#443

Fixed, waiting release soon.

Often times, the roads to AOT compatibility leads to improvements across the board, even for non-AOT scenarios.

Who knows potential issues... , I cannot prepare decomposed tasks to archive the goal. Our mission here is to adopt existing codebase to be ready for AOT.

The technical enabler is resolved, so the list of impacted areas will be be growing so fast soon.

@RenderMichael

@RenderMichael are you able to test the preview version of Selenium which seems is compatible with AOT (excepting CDP)? Your input would be valuable. I can share nuget package file here (built locally).

@nvborisenko

@nvborisenko I would be happy to test out the AOT compatibility of Selenium :)

@RenderMichael

Selenium.WebDriver.4.26.0-nightly202409202352.zip

@RenderMichael This is zip, which contains nupkg inside. I built it locally, and hoping you know what to do with it.

@RenderMichael

@RenderMichael @NCLnclNCL please don't forget to share results. Thanks guys.

@nvborisenko

~~@nvborisenko Unfortunately the app crashed as soon as I tried running the native .exe file:~~

I can't give more detailed feedback without building the library locally. Are there any instructions I can follow to build the .NET bindings locally? A while back I tried to do so following this guide but ran into some blockers (I no longer remember what they were).

Edit: it was my error

This was my program for the above. Completely ideomatic, no obscure Selenium features or anything.

using OpenQA.Selenium.Firefox;

var options = new FirefoxOptions
{
    AcceptInsecureCertificates = true,
};

using (var driver = new FirefoxDriver(options))
{
    await driver.Navigate().GoToUrlAsync("https://www.google.com");

    string url = driver.Url;
    if (!url.Contains("google"))
    {
        throw new Exception("URL does not contain google: " + url);
    }
}

Console.ReadKey();

@RenderMichael

I received a lot of issues privately related to json serialization. In major cases users used custom class and they provided an instance of it as object. Object is expected according API, and they got JsonTypeInfo metadata for type '*' was not provided by TypeInfoResolver of type 'OpenQA.Selenium.CommandJsonSerializerContext' exception. @RenderMichael provided elegant fix (will be in 4.27). Seems we will forget about this issue for "classic" WebDriver commands. Thank you, Michael, great job!

Happy to contribute!

I have a PR addressing every AOT concern aside from JSON. It was a lot simpler than I thought. #14637

Happy to contribute!

I have a PR addressing every AOT concern aside from JSON. It was a lot simpler than I thought. #14637

Hi,do you know anything about python, i want to convert python nodriver library to c#

Hi

My current goal is to migrate my selenium project into a Native Aot application.

I get errors when i start a new DevToolsSessions

OpenQA.Selenium.WebDriverException: 'Unexpected error creating WebSocket DevTools session.'
InvalidOperationException: Reflection-based serialization has been disabled for this application. Either use the source generator APIs or explicitly configure the 'JsonSerializerOptions.TypeInfoResolver' property.

        var driver = new ChromeDriver();
        var devToolsSession = driver.GetDevToolsSession(); <- Error here

I am not familie with the internals of Selenium but maybe you can tell me if my project is a lost cause or if the problems are going to be handled by some of the hard work you seem to be doing in regards to AOT ?

GetDevToolsSession is not compatible with AOT yet, please track CDP section in the original post.

@RenderMichael

@RenderMichael do you want to invest into CDP (DevTools) AOT compatibility? I don't want, BiDi is a priority for me.

@nvborisenko

@nvborisenko Per the tracking issue for depreciating CDP #13994:

We'll still allow access to lower level CDP functionality (see #13990), but the high level approach will be removed.

I interpret this to mean we will still keep the SendCommand method which takes a string commandName, and JsonNode commandParameters, with the JsonElement? response. Basically remove the strongly typed commands.

For that reason, we shouldn't unnecessarily block AOT, especially since supporting it is so simple: #15159

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 14 days.

This issue was closed because it has been stalled for 14 days with no activity.

For my projects, I have found the flag JsonSerializerIsReflectionEnabledByDefault quite useful

		<JsonSerializerIsReflectionEnabledByDefault>false</JsonSerializerIsReflectionEnabledByDefault>

Even if there are parts of the code using reflection, at lest I know the Json part is reflection free... and therefore AOT and trimming safe

TLC proposed CDP is out of scope, even if PR provided.

So this feature request will alive forever. Crossfingers we will be able to move on somehow.

Navigation Menu

Repository navigation

[🚀 Feature]: [dotnet] Road to be AOT friendly #14480

Feature and motivation

Usage example

10 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[🚀 Feature]: [dotnet] Road to be AOT friendly #14480

Description

Feature and motivation

Usage example

Activity

github-actions commented on Sep 9, 2024

nvborisenko commented on Sep 9, 2024

RenderMichael commented on Sep 10, 2024

NCLnclNCL commented on Sep 26, 2024

nvborisenko commented on Oct 4, 2024

nvborisenko commented on Oct 17, 2024

RenderMichael commented on Oct 17, 2024

nvborisenko commented on Oct 17, 2024

nvborisenko commented on Oct 18, 2024

RenderMichael commented on Oct 20, 2024

RenderMichael commented on Oct 20, 2024

10 remaining items

nvborisenko commented on Nov 18, 2024

RenderMichael commented on Nov 18, 2024

NCLnclNCL commented on Nov 19, 2024

larsbloch commented on Nov 21, 2024

nvborisenko commented on Nov 22, 2024

nvborisenko commented on Feb 27, 2025

RenderMichael commented on Feb 27, 2025

github-actions commented on Jan 12, 2026

github-actions commented on Jan 26, 2026

flucas1 commented on Jun 7, 2026

nvborisenko commented on Nov 7, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions