Selenium.WebDriver.ChromeDriver 96.0.4664.4500

There is a newer version of this package available.
See the version list below for details.
Install-Package Selenium.WebDriver.ChromeDriver -Version 96.0.4664.4500
dotnet add package Selenium.WebDriver.ChromeDriver --version 96.0.4664.4500
<PackageReference Include="Selenium.WebDriver.ChromeDriver" Version="96.0.4664.4500" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Selenium.WebDriver.ChromeDriver --version 96.0.4664.4500
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Selenium.WebDriver.ChromeDriver, 96.0.4664.4500"
#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=96.0.4664.4500

// Install Selenium.WebDriver.ChromeDriver as a Cake Tool
#tool nuget:?package=Selenium.WebDriver.ChromeDriver&version=96.0.4664.4500
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 96:

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

If you are using Chrome version 95:

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

If you are using Chrome version 94:

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

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.

This package has no dependencies.

NuGet packages (108)

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

Package Downloads
Pangolin

A framework for declarative UI testing for ASP.NET apps. Browsers: Chrome (>=96) Firefox (>=70) IE (>=11) Dependencies: MSharp Project: MSharp.Framework (>= 4.0.110) Olive Project: Olive.Testing (>= 2.1.113)

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

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.

Ocaramba

Framework to automate tests using Selenium WebDriver

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 Downloads Last updated
98.0.4758.4800-beta 800 1/12/2022
97.0.4692.7100 60,503 1/6/2022
97.0.4692.3600-beta 5,413 12/3/2021
97.0.4692.2000-beta 2,107 11/19/2021
96.0.4664.4500 482,318 11/16/2021
96.0.4664.3500-beta 2,425 11/8/2021
96.0.4664.1800-beta.2 419 11/3/2021
96.0.4664.1800-beta 1,964 10/25/2021
95.0.4638.6900 121,816 11/8/2021
95.0.4638.5401 67,492 11/3/2021
95.0.4638.5400 77,412 10/28/2021
95.0.4638.1700 157,338 10/20/2021
95.0.4638.1700-beta 10,125 9/28/2021
95.0.4638.1000-beta 1,763 9/21/2021
94.0.4606.11300 4,956 11/8/2021
94.0.4606.6100 394,970 9/28/2021
94.0.4606.4101 124,530 9/22/2021
94.0.4606.4101-beta 2,375 9/10/2021
93.0.4577.6300 114,397 9/14/2021
93.0.4577.1500 240,143 9/1/2021
93.0.4577.1500-beta 8,577 7/29/2021
92.0.4515.10700 465,378 7/29/2021
92.0.4515.4300 179,598 7/21/2021
92.0.4515.4300-beta 4,802 6/12/2021
91.0.4472.10100 441,018 6/12/2021
91.0.4472.1900 403,451 5/26/2021
91.0.4472.1900-beta 4,754 4/23/2021
90.0.4430.2400 774,698 4/14/2021
90.0.4430.2400-beta 5,927 3/16/2021
89.0.4389.2300 813,236 3/4/2021
89.0.4389.2300-beta 7,391 1/29/2021
88.0.4324.9600 677,701 1/21/2021
88.0.4324.2700 42,265 1/19/2021
88.0.4324.2700-beta 3,439 12/4/2020
87.0.4280.8800 1,005,807 12/2/2020
87.0.4280.2000 366,659 11/18/2020
87.0.4280.2000-beta 26,729 10/17/2020
86.0.4240.2200 595,289 10/9/2020
86.0.4240.2200-beta 15,174 9/4/2020
85.0.4183.8700 867,053 8/28/2020
85.0.4183.8300 167,335 8/26/2020
85.0.4183.3800-beta 5,046 7/24/2020
84.0.4147.3001 374,438 7/15/2020
84.0.4147.3001-beta 631 7/12/2020
84.0.4147.3000-beta 7,267 5/29/2020
83.0.4103.3915 33,221 7/15/2020
83.0.4103.3915-beta 1,745 7/11/2020
83.0.4103.3910 184,598 6/28/2020
83.0.4103.3910-beta 8,026 5/24/2020
83.0.4103.3900 891,933 5/20/2020
83.0.4103.3900-beta 16,380 5/6/2020
83.0.4103.1400-beta 5,317 4/17/2020
81.0.4044.13800 129,288 5/6/2020
81.0.4044.6900 298,602 4/9/2020
81.0.4044.6900-beta 1,999 3/18/2020
81.0.4044.2000-beta 3,673 2/14/2020
80.0.3987.10600 789,149 2/14/2020
80.0.3987.1600 252,763 2/5/2020
80.0.3987.1600-beta 3,119 12/20/2019
79.0.3945.3600 787,684 12/12/2019
79.0.3945.3600-beta 17,623 11/19/2019
79.0.3945.1600-beta 1,643 10/31/2019
78.0.3904.10500 292,730 11/19/2019
78.0.3904.7000 450,014 10/23/2019
78.0.3904.1100-beta 3,970 9/13/2019
77.0.3865.4000 449,322 9/13/2019
77.0.3865.4000-beta 2,491 8/21/2019
77.0.3865.10-beta 5,714 8/7/2019
76.0.3809.12600 240,685 8/22/2019
76.0.3809.6801 94,454 8/12/2019
76.0.3809.68 148,080 8/5/2019
76.0.3809.68-beta 4,936 7/17/2019
76.0.3809.25-beta 3,531 6/14/2019
76.0.3809.12-beta 717 6/8/2019
75.0.3770.140 271,570 7/14/2019
75.0.3770.90 202,609 6/14/2019
75.0.3770.8 59,050 6/8/2019
74.0.3729.6 434,384 4/25/2019
73.0.3683.68 266,133 3/13/2019
72.0.3626.69 375,611 3/5/2019
71.0.3578.137 38,263 3/5/2019
2.46.0 344,798 2/2/2019
2.45.0 340,794 12/11/2018
2.44.0 311,739 11/21/2018
2.43.0 825,906 10/18/2018
2.42.0.1 355,415 9/14/2018
2.41.0 514,615 7/28/2018
2.40.0 723,928 6/8/2018
2.39.0 91,436 5/30/2018
2.38.0.1 406,190 4/26/2018
2.38.0 406,113 4/18/2018
2.37.0 580,903 3/17/2018
2.36.0 240,185 3/2/2018
2.35.0 434,938 1/11/2018
2.34.0 122,524 12/10/2017
2.33.0 449,061 10/4/2017
2.32.0 147,258 8/31/2017
2.31.0 120,892 7/23/2017
2.30.0.1 407,693 6/8/2017
2.29.0 339,878 4/4/2017
2.28.0.2-beta 1,942 3/21/2017
2.28.0.1-beta 3,080 3/9/2017
2.28.0 111,485 3/9/2017
2.27.0.7-beta 2,211 3/3/2017
2.27.0.6-beta 721 3/2/2017
2.27.0.2-beta 936 2/28/2017
2.27.0 246,775 12/22/2016
2.26.0 55,292 12/6/2016
2.25.0.8 113,903 11/15/2016
2.25.0.8-beta 4,899 10/29/2016
2.25.0 93,691 10/24/2016
2.24.0 126,366 9/16/2016
2.23.0.1 99,920 8/10/2016
2.23.0 3,860 8/9/2016
2.22.0 96,615 6/8/2016
2.21.0.1-beta 2,537 5/5/2016
2.21.0 198,327 1/26/2016
2.20.0 155,971 10/9/2015
2.19.0 42,512 9/6/2015
2.18.0 10,311 8/22/2015
2.17.0 8,088 8/12/2015
2.16.0 15,693 6/27/2015
2.15.0 39,016 4/1/2015
2.14.0.1-beta 961 3/6/2015
2.14.0 18,335 3/3/2015
2.13.0 17,616 1/6/2015
2.12.0 18,478 10/30/2014
2.10.0.1-beta2 1,864 8/14/2014
2.10.0.1-beta 776 8/14/2014
2.10.0 27,665 5/8/2014
2.9.0.1 5,619 4/7/2014
2.9.0.1-beta3 900 4/5/2014
2.9.0.1-beta2 888 4/3/2014
2.9.0 9,311 3/27/2014
2.8.0 9,983 1/24/2014
2.3.0 8,050 9/7/2013
2.2.0 6,067 8/28/2013

96.0.4664.4500
     - Chrome Driver 96.0.4664.45 release