Install Gecko Driver (Win32, Win64, macOS, macOS arm64, and Linux64) for Selenium WebDriver
into your Unit Test Project.
"geckodriver(.exe)" is copied to bin folder from package folder when the build process.
NuGet package restoring ready, and no need to commit "geckodriver(.exe)" binary into source
code control repository.
/ The MSBuild script that contained this package is free and unencumbered software released
into the public domain.
/ "geckodriver(.exe)" is licensed under the Mozilla Public License Version 2.0.
By default - it depends on the OS running the build process
By default, the platform type of the web driver file copied to the output folder depends on the OS running the build process.
When you build the project which references the NuGet package of geckodriver on 32bit Windows OS, win32 version of geckodriver will be copied to the output folder.
When you build the project which references the NuGet package of geckodriver on 64bit Windows OS, win64 version of geckodriver will be copied to the output folder.
When you build it on macOS on Intel CPU hardware, macOS x64 version of geckodriver will be copied to the output folder.
When you build it on macOS on Apple CPU hardware, macOS Arm64 version of geckodriver will be copied to the output folder.
When you build it on any Linux distributions, Linux x64 version of geckodriver will be copied to the output folder.
Method 1 - Specify "Runtime Identifier"
When you specify the "Runtime Identifier (RID)" explicitly, the platform type of the driver file is the same to the RID which you specified. (it doesn't depends on the which OS to use for build process.)
You can specify RID as a MSBuild property in a project file,
or, as a command-line -r option for dotnet build command.
> dotnet build -r:osx.10.12-x64
When the RID that starts with "win" and contains "x86" is specified, win32 version of geckodriver will be copied to the output folder.
When the RID that starts with "win" and contains "x64" is specified, win64 version of geckodriver will be copied to the output folder.
When the RID that starts with "osx" and ends with "x64" is specified, macOS x64 version of geckodriver will be copied to the output folder.
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 "linux" is specified, Linux x64 version of geckodriver will be copied to the output folder.
If you specify another pattern of RID like "ubuntu.18.04-x64", the platform type of the web driver file which will be copied to the output folder depends on the OS running the build process. (default behavior.)
The driver file of macOS x64 version will be copied to the output folder.
How to include the driver file into published files?
"geckodriver(.exe)" isn't included in published files on default configuration. This behavior is by design.
If you want to include "geckodriver(.exe)" into published files, please define _PUBLISH_GECKODRIVER compilation symbol.
Another way, you can define PublishGeckoDriver property with value is "true" in MSBuild file (.csproj, .vbproj, etc...) to publish the driver file instead of define compilation symbol.
You can also define PublishGeckoDriver property from the command line -p option for dotnet publish command.
> dotnet publish -p:PublishGeckoDriver=true
Note
PublishGeckoDriver MSBuild property always override the condition of define _PUBLISH_GECKODRIVER compilation symbol or not. If you define PublishGeckoDriver MSBuild property with false, then the driver file isn't included in publish files whenever define _PUBLISH_GECKODRIVER compilation symbol or not.
