[🚀 Feature]: [dotnet] Small step forward to Async

[nvborisenko]

Description

Nobody knows when Async #14067 will be in place, and moreover how to do it smoothly without pain for end-users.

I propose to make small improvement now, even before v5.

Current

var driver = new ChromeDriver();

Proposal:

var driver = await ChromeDriver.StartAsync();

Have you considered any alternatives or workarounds?

In any case constructor cannot be async, we will rework it entirely. Ha, and it means everybody has to use another API.

I propose alternative approach here.

Bad?

var driver = new ChromeDriver();
await driver.StartAsync();

Better:

var driver = await ChromeDriver.StartAsync();

We can try to make it without breaking changes. Seems it is small step, but it contributes significantly. This is most tricky part of migration.

[selenium-ci]

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

Selenium Triage Team: remember to follow the Triage Guide

[spider-yamet]

@selenium-ci May I pick up this issue?
Hope this project is open for contribution.

[nvborisenko]

Successfully migrated low-level parts to be async. Need to be done:

1. Make any WebDriver IAsyncDisposable (small breaking change for implementors): [dotnet] Any WebDriver can be disposed asynchronously #17119
2. Waiting good decision on single entry for WebDriver configuration: [🚀 Feature]: [dotnet] Web driver (options) builder #17115. Otherwise we will have millions of method overloads.