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

[nvborisenko]

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

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

W3C WebDriver

• New Session
• ...

W3C BiDi

• ...

Usage example

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

[github-actions]

@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!

[nvborisenko]

Blocked by bazelbuild/rules_dotnet#443

[RenderMichael]

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.