Selenium.WebDriver.ChromeDriver 91.0.4472.1900-beta

Install Chrome Driver (Win32, macOS, and Linux64) for Selenium WebDriver into your Unit Test Project.
     "chromedriver(.exe)" is copied to the bin folder from the package folder when the build process.
     NuGet package restoring ready, and no need to commit "chromedriver(.exe)" binary into source code control repository.
     / The MSBuild script that contained this package is free and unencumbered software released into the public domain.
     / "chromedriver(.exe)" is licensed under the New BSD License.

This is a prerelease version of Selenium.WebDriver.ChromeDriver.
There is a newer version of this package available.
See the version list below for details.
Install-Package Selenium.WebDriver.ChromeDriver -Version 91.0.4472.1900-beta
dotnet add package Selenium.WebDriver.ChromeDriver --version 91.0.4472.1900-beta
<PackageReference Include="Selenium.WebDriver.ChromeDriver" Version="91.0.4472.1900-beta" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Selenium.WebDriver.ChromeDriver --version 91.0.4472.1900-beta
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Selenium.WebDriver.ChromeDriver, 91.0.4472.1900-beta"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Selenium.WebDriver.ChromeDriver as a Cake Addin
#addin nuget:?package=Selenium.WebDriver.ChromeDriver&version=91.0.4472.1900-beta&prerelease

// Install Selenium.WebDriver.ChromeDriver as a Cake Tool
#tool nuget:?package=Selenium.WebDriver.ChromeDriver&version=91.0.4472.1900-beta&prerelease
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

NuGet package - Selenium WebDriver ChromeDriver

NuGet Package NuGet Package NuGet Package

What's this?

This NuGet package installs Chrome Driver (Win32, macOS, and Linux64) for Selenium WebDriver into your Unit Test Project.

"chromedriver(.exe)" does not appear in Solution Explorer, but it is copied to the output folder from the package source folder when the build process.

NuGet package restoring ready, and no need to commit "chromedriver(.exe)" binary into source code control repository.

How to install?

For example, at the package manager console on Visual Studio, enter the following command.

If you are using Chrome version 91:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 91.0.4472.1900-beta -IncludePrerelease

If you are using Chrome version 90:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 90.0.4430.2400

If you are using Chrome version 89:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 89.0.4389.2300

To learn what version of ChromeDriver you need to use, please see also the following page:

https://chromedriver.chromium.org/downloads/version-selection

Cross-platform building and publishing

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 chromedriver on Windows OS, win32 version of chromedriver will be copied to the output folder.
  • When you build it on macOS, macOS x64 version of chromedriver will be copied to the output folder.
  • When you build it on any Linux distributions, Linux x64 version of chromedriver 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,

<PropertyGroup>
  <RuntimeIdentifier>win-x64</RuntimeIdentifier>
</PropertyGroup>

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" is specified, win32 version of chromedriver will be copied to the output folder.
  • When the RID that starts with "osx" is specified, macOS x64 version of chromedriver will be copied to the output folder.
  • When the RID that starts with "linux" is specified, Linux x64 version of chromedriver 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.)

Method 2 - Specify "WebDriverPlatform" msbuild property

You can control which platform version of chromedriver will be copied by specifying "WebDriverPlatform" MSBuild property.

"WebDriverPlatform" MSBuild property can take one of the following values:

  • "win32"
  • "mac64"
  • "linux64"

You can specify "WebDriverPlatform" MSBuild property in a project file,

<PropertyGroup>
  <WebDriverPlatform>win32</WebDriverPlatform>
</PropertyGroup>

or, command-line -p option for dotnet build command.

> dotnet build -p:WebDriverPlatform=mac64

The specifying "WebDriverPlatform" MSBuild property is the highest priority method to control which platform version of the chromedriver will be copied.

If you run the following command on Windows OS,

> dotnet build -r:ubuntu.18.04-x64 -p:WebDriverPlatform=mac64

The driver file of macOS x64 version will be copied to the output folder.

How to include the driver file into published files?

"chromedriver(.exe)" isn't included in published files on default configuration. This behavior is by design.

If you want to include "chromedriver(.exe)" into published files, please define _PUBLISH_CHROMEDRIVER compilation symbol.

define _PUBLISH_CHROMEDRIVER compilation symbol

Another way, you can define PublishChromeDriver property with value is "true" in MSBuild file (.csproj, .vbproj, etc...) to publish the driver file instead of define compilation symbol.

  <Project ...>
    ...
    <PropertyGroup>
      ...
      <PublishChromeDriver>true</PublishChromeDriver>
      ...
    </PropertyGroup>
...
</Project>

You can also define PublishChromeDriver property from the command line -p option for dotnet publish command.

> dotnet publish -p:PublishChromeDriver=true
Note

PublishChromeDriver MSBuild property always override the condition of define _PUBLISH_CHROMEDRIVER compilation symbol or not. If you define PublishChromeDriver MSBuild property with false, then the driver file isn't included in publish files whenever define _PUBLISH_CHROMEDRIVER compilation symbol or not.

Appendix

The numbering of the package version

The rule of the version number of this package is:

chromedriver version MAJOR.MINOR.BUILD.PATCH + package version (2 digit)

For example, 2nd package release for the chromedriver ver.1.2.3.4, the package version is 1.2.3.4 + 021.2.3.402.

Sometime multiple packages for the same chromedriver version may be released by following example reasons.

  • Packaging miss. (the package included invalid version of the driver files)
  • Fixing bug of the build script, or improving the build script.

Where is chromedriver.exe saved to?

chromedriver(.exe) exists at
" {solution folder} /packages/Selenium.WebDriver.ChromeDriver. {ver} /driver/ {platform}"
folder.

 {Solution folder}/
  +-- packages/
  |   +-- Selenium.WebDriver.ChromeDriver.{version}/
  |       +-- driver/
  |       |   +-- win32
  |       |       +-- chromedriver.exe
  |       |   +-- mac64
  |       |       +-- chromedriver
  |       |   +-- linux64
  |       |       +-- chromedriver
  |       +-- build/
  +-- {project folder}/
      +-- bin/
          +-- Debug/
          |   +-- chromedriver(.exe) (copy from above by build process)
          +-- Release/
              +-- chromedriver(.exe) (copy from above by build process)

And package installer configure MSBuild task such as .csproj to
copy chromedriver(.exe) into the output folder during the build process.

License

The build script (.targets file) in this NuGet package is licensed under The Unlicense.

The binary files of ChromeDriver are licensed under the BSD-3-Clause.

NuGet package - Selenium WebDriver ChromeDriver

NuGet Package NuGet Package NuGet Package

What's this?

This NuGet package installs Chrome Driver (Win32, macOS, and Linux64) for Selenium WebDriver into your Unit Test Project.

"chromedriver(.exe)" does not appear in Solution Explorer, but it is copied to the output folder from the package source folder when the build process.

NuGet package restoring ready, and no need to commit "chromedriver(.exe)" binary into source code control repository.

How to install?

For example, at the package manager console on Visual Studio, enter the following command.

If you are using Chrome version 91:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 91.0.4472.1900-beta -IncludePrerelease

If you are using Chrome version 90:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 90.0.4430.2400

If you are using Chrome version 89:

PM> Install-Package Selenium.WebDriver.ChromeDriver -Version 89.0.4389.2300

To learn what version of ChromeDriver you need to use, please see also the following page:

https://chromedriver.chromium.org/downloads/version-selection

Cross-platform building and publishing

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 chromedriver on Windows OS, win32 version of chromedriver will be copied to the output folder.
  • When you build it on macOS, macOS x64 version of chromedriver will be copied to the output folder.
  • When you build it on any Linux distributions, Linux x64 version of chromedriver 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,

<PropertyGroup>
  <RuntimeIdentifier>win-x64</RuntimeIdentifier>
</PropertyGroup>

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" is specified, win32 version of chromedriver will be copied to the output folder.
  • When the RID that starts with "osx" is specified, macOS x64 version of chromedriver will be copied to the output folder.
  • When the RID that starts with "linux" is specified, Linux x64 version of chromedriver 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.)

Method 2 - Specify "WebDriverPlatform" msbuild property

You can control which platform version of chromedriver will be copied by specifying "WebDriverPlatform" MSBuild property.

"WebDriverPlatform" MSBuild property can take one of the following values:

  • "win32"
  • "mac64"
  • "linux64"

You can specify "WebDriverPlatform" MSBuild property in a project file,

<PropertyGroup>
  <WebDriverPlatform>win32</WebDriverPlatform>
</PropertyGroup>

or, command-line -p option for dotnet build command.

> dotnet build -p:WebDriverPlatform=mac64

The specifying "WebDriverPlatform" MSBuild property is the highest priority method to control which platform version of the chromedriver will be copied.

If you run the following command on Windows OS,

> dotnet build -r:ubuntu.18.04-x64 -p:WebDriverPlatform=mac64

The driver file of macOS x64 version will be copied to the output folder.

How to include the driver file into published files?

"chromedriver(.exe)" isn't included in published files on default configuration. This behavior is by design.

If you want to include "chromedriver(.exe)" into published files, please define _PUBLISH_CHROMEDRIVER compilation symbol.

define _PUBLISH_CHROMEDRIVER compilation symbol

Another way, you can define PublishChromeDriver property with value is "true" in MSBuild file (.csproj, .vbproj, etc...) to publish the driver file instead of define compilation symbol.

  <Project ...>
    ...
    <PropertyGroup>
      ...
      <PublishChromeDriver>true</PublishChromeDriver>
      ...
    </PropertyGroup>
...
</Project>

You can also define PublishChromeDriver property from the command line -p option for dotnet publish command.

> dotnet publish -p:PublishChromeDriver=true
Note

PublishChromeDriver MSBuild property always override the condition of define _PUBLISH_CHROMEDRIVER compilation symbol or not. If you define PublishChromeDriver MSBuild property with false, then the driver file isn't included in publish files whenever define _PUBLISH_CHROMEDRIVER compilation symbol or not.

Appendix

The numbering of the package version

The rule of the version number of this package is:

chromedriver version MAJOR.MINOR.BUILD.PATCH + package version (2 digit)

For example, 2nd package release for the chromedriver ver.1.2.3.4, the package version is 1.2.3.4 + 021.2.3.402.

Sometime multiple packages for the same chromedriver version may be released by following example reasons.

  • Packaging miss. (the package included invalid version of the driver files)
  • Fixing bug of the build script, or improving the build script.

Where is chromedriver.exe saved to?

chromedriver(.exe) exists at
" {solution folder} /packages/Selenium.WebDriver.ChromeDriver. {ver} /driver/ {platform}"
folder.

 {Solution folder}/
  +-- packages/
  |   +-- Selenium.WebDriver.ChromeDriver.{version}/
  |       +-- driver/
  |       |   +-- win32
  |       |       +-- chromedriver.exe
  |       |   +-- mac64
  |       |       +-- chromedriver
  |       |   +-- linux64
  |       |       +-- chromedriver
  |       +-- build/
  +-- {project folder}/
      +-- bin/
          +-- Debug/
          |   +-- chromedriver(.exe) (copy from above by build process)
          +-- Release/
              +-- chromedriver(.exe) (copy from above by build process)

And package installer configure MSBuild task such as .csproj to
copy chromedriver(.exe) into the output folder during the build process.

License

The build script (.targets file) in this NuGet package is licensed under The Unlicense.

The binary files of ChromeDriver are licensed under the BSD-3-Clause.

Release Notes

91.0.4472.1900
     - Chrome Driver 91.0.4472.19 release

Dependencies

This package has no dependencies.

NuGet packages (105)

Showing the top 5 NuGet packages that depend on Selenium.WebDriver.ChromeDriver:

Package Downloads
SpecsFor.Mvc
SpecsFor.Mvc is a stand-alone acceptance testing framework for ASP.NET MVC. It enables you to write strongly-typed, refactor friendly integration tests using the browser and testing framework of your choice.
Objectivity.Test.Automation.Common.NUnit
[DEPRECATED] Use Install-Package Ocaramba.Features Install-Package Ocaramba.MsTest Install-Package Ocaramba.NUnit Install-Package Ocaramba.xUnit instead
Pangolin
A framework for declarative UI testing for ASP.NET apps. Browsers: Chrome (>=89) Firefox (>=70) IE (>=11) Dependencies: MSharp Project: MSharp.Framework (>= 4.0.110) Olive Project: Olive.Testing (>= 2.1.113)
Selenium.Helper
This package contains .NET helper classes to make the creation of Selenium tests easier. It contains a Connector class that supports various initializations of the Driver. It also contains a utility class to assist in working with elements.
Animatronio
Selenium Framework

GitHub repositories (37)

Showing the top 5 popular GitHub repositories that depend on Selenium.WebDriver.ChromeDriver:

Repository Stars
Radarr/Radarr
A fork of Sonarr to work with movies à la Couchpotato.
btcpayserver/btcpayserver
Accept Bitcoin payments. Free, open-source & self-hosted, Bitcoin payment processor.
aspnet/KestrelHttpServer
[Archived] A cross platform web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore
mono/SkiaSharp
SkiaSharp is a cross-platform 2D graphics API for .NET platforms based on Google's Skia Graphics Library. It provides a comprehensive 2D API that can be used across mobile, server and desktop models to render images.
lidarr/Lidarr
Looks and smells like Sonarr but made for music.

Version History

Version Downloads Last updated
92.0.4515.4300-beta 166 6/12/2021
91.0.4472.10100 7,867 6/12/2021
91.0.4472.1900 94,687 5/26/2021
91.0.4472.1900-beta 2,785 4/23/2021
90.0.4430.2400 381,427 4/14/2021
90.0.4430.2400-beta 3,963 3/16/2021
89.0.4389.2300 592,166 3/4/2021
89.0.4389.2300-beta 6,873 1/29/2021
88.0.4324.9600 543,210 1/21/2021
88.0.4324.2700 32,445 1/19/2021
88.0.4324.2700-beta 3,115 12/4/2020
87.0.4280.8800 738,339 12/2/2020
87.0.4280.2000 295,264 11/18/2020
87.0.4280.2000-beta 26,156 10/17/2020
86.0.4240.2200 510,799 10/9/2020
86.0.4240.2200-beta 14,811 9/4/2020
85.0.4183.8700 758,217 8/28/2020
85.0.4183.8300 157,499 8/26/2020
85.0.4183.3800-beta 4,909 7/24/2020
84.0.4147.3001 329,033 7/15/2020
84.0.4147.3001-beta 554 7/12/2020
84.0.4147.3000-beta 6,065 5/29/2020
83.0.4103.3915 26,192 7/15/2020
83.0.4103.3915-beta 832 7/11/2020
83.0.4103.3910 171,618 6/28/2020
83.0.4103.3910-beta 7,167 5/24/2020
83.0.4103.3900 823,313 5/20/2020
83.0.4103.3900-beta 16,286 5/6/2020
83.0.4103.1400-beta 4,329 4/17/2020
81.0.4044.13800 119,012 5/6/2020
81.0.4044.6900 273,836 4/9/2020
81.0.4044.6900-beta 1,816 3/18/2020
81.0.4044.2000-beta 3,481 2/14/2020
80.0.3987.10600 699,094 2/14/2020
80.0.3987.1600 242,821 2/5/2020
80.0.3987.1600-beta 3,018 12/20/2019
79.0.3945.3600 731,164 12/12/2019
79.0.3945.3600-beta 13,764 11/19/2019
79.0.3945.1600-beta 1,563 10/31/2019
78.0.3904.10500 265,332 11/19/2019
78.0.3904.7000 425,744 10/23/2019
78.0.3904.1100-beta 3,818 9/13/2019
77.0.3865.4000 413,693 9/13/2019
77.0.3865.4000-beta 2,416 8/21/2019
77.0.3865.10-beta 4,401 8/7/2019
76.0.3809.12600 228,775 8/22/2019
76.0.3809.6801 92,329 8/12/2019
76.0.3809.68 138,629 8/5/2019
76.0.3809.68-beta 4,874 7/17/2019
76.0.3809.25-beta 3,336 6/14/2019
76.0.3809.12-beta 637 6/8/2019
75.0.3770.140 239,164 7/14/2019
75.0.3770.90 189,606 6/14/2019
75.0.3770.8 57,372 6/8/2019
74.0.3729.6 413,599 4/25/2019
73.0.3683.68 243,208 3/13/2019
72.0.3626.69 353,351 3/5/2019
71.0.3578.137 31,315 3/5/2019
2.46.0 336,663 2/2/2019
2.45.0 303,561 12/11/2018
2.44.0 263,644 11/21/2018
2.43.0 801,661 10/18/2018
2.42.0.1 327,626 9/14/2018
2.41.0 489,629 7/28/2018
2.40.0 677,518 6/8/2018
2.39.0 88,484 5/30/2018
2.38.0.1 382,526 4/26/2018
2.38.0 333,522 4/18/2018
2.37.0 553,040 3/17/2018
2.36.0 235,389 3/2/2018
2.35.0 412,478 1/11/2018
2.34.0 117,082 12/10/2017
2.33.0 427,406 10/4/2017
2.32.0 140,709 8/31/2017
2.31.0 114,591 7/23/2017
2.30.0.1 367,059 6/8/2017
2.29.0 323,635 4/4/2017
2.28.0.2-beta 1,868 3/21/2017
2.28.0.1-beta 3,009 3/9/2017
2.28.0 107,651 3/9/2017
2.27.0.7-beta 2,141 3/3/2017
2.27.0.6-beta 648 3/2/2017
2.27.0.2-beta 869 2/28/2017
2.27.0 238,928 12/22/2016
2.26.0 53,906 12/6/2016
2.25.0.8 108,537 11/15/2016
2.25.0.8-beta 4,545 10/29/2016
2.25.0 90,958 10/24/2016
2.24.0 118,369 9/16/2016
2.23.0.1 97,305 8/10/2016
2.23.0 3,735 8/9/2016
2.22.0 93,092 6/8/2016
2.21.0.1-beta 2,461 5/5/2016
2.21.0 192,931 1/26/2016
2.20.0 150,909 10/9/2015
2.19.0 41,630 9/6/2015
2.18.0 10,124 8/22/2015
2.17.0 7,589 8/12/2015
2.16.0 15,286 6/27/2015
2.15.0 38,080 4/1/2015
2.14.0.1-beta 886 3/6/2015
2.14.0 17,369 3/3/2015
2.13.0 16,843 1/6/2015
2.12.0 17,913 10/30/2014
2.10.0.1-beta2 1,770 8/14/2014
2.10.0.1-beta 694 8/14/2014
2.10.0 26,531 5/8/2014
2.9.0.1 5,335 4/7/2014
2.9.0.1-beta3 716 4/5/2014
2.9.0.1-beta2 703 4/3/2014
2.9.0 9,065 3/27/2014
2.8.0 9,075 1/24/2014
2.3.0 7,854 9/7/2013
2.2.0 5,444 8/28/2013