
When the RID that starts with "osx" and ends with "arm64" is specified, macOS Arm64 version of geckodriver will be copied to the output folder.When the RID that starts with "osx" and ends with "圆4" is specified, macOS 圆4 version of geckodriver will be copied to the output folder.When the RID that starts with "win" and contains "圆4" is specified, win64 version of geckodriver will be copied to the output folder.When the RID that starts with "win" and contains "x86" is specified, win32 version of geckodriver will be copied to the output folder.Or, as a command-line -r option for dotnet build command. You can specify RID as a MSBuild property in a project file, (it doesn't depends on the which OS to use for build process.) When you specify the "Runtime Identifier ( RID)" explicitly, the platform type of the driver file is the same to the RID which you specified. When you build it on any Linux distributions, Linux 圆4 version of geckodriver will be copied to the output folder.


So now, you can run applications that use Selenium and manipulates web browsers without this package. Since Selenium WebDriver version 4.6 was released in November 2022 or later, it has contained "Selenium Manager", which will automatically download the most suitable version and platform WebDriver executable file.

NuGet package restoring ready, and no need to commit "geckodriver(.exe)" binary into source code control repository. "geckodriver(.exe)" does not appear in Solution Explorer, but it is copied to the output folder from the package folder when the build process. This NuGet package install Gecko Driver for Selenium WebDriver into your Unit Test Project. NuGet package - Selenium WebDriver GeckoDriver
