Selenium.WebDriver.ChromeDriver 114.0.5735.1600

dotnet add package Selenium.WebDriver.ChromeDriver --version 114.0.5735.1600
NuGet\Install-Package Selenium.WebDriver.ChromeDriver -Version 114.0.5735.1600
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Selenium.WebDriver.ChromeDriver" Version="114.0.5735.1600" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Selenium.WebDriver.ChromeDriver --version 114.0.5735.1600
#r "nuget: Selenium.WebDriver.ChromeDriver, 114.0.5735.1600"
#r directive can be used in F# Interactive and Polyglot Notebooks. 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=114.0.5735.1600

// Install Selenium.WebDriver.ChromeDriver as a Cake Tool
#tool nuget:?package=Selenium.WebDriver.ChromeDriver&version=114.0.5735.1600

NuGet package - Selenium WebDriver ChromeDriver

NuGet Package NuGet Package NuGet Package

What's this?

This NuGet package installs Chrome Driver (Win32, macOS, macOS arm64, 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.

Warning
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. So now, you can run applications that use Selenium and manipulates web browsers without this package. However, due to compatibility and some offline scenarios, we intend to keep this package for the time being.

How to install?

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

If you are using Chrome version 114:

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

If you are using Chrome version 113:

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

If you are using Chrome version 112:

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

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 on Intel CPU hardware, macOS x64 version of chromedriver will be copied to the output folder.
  • When you build it on macOS on Apple CPU hardware, macOS Arm64 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" and ends with "x64" is specified, macOS x64 version of chromedriver will be copied to the output folder.
  • When the RID that starts with "osx" and ends with "arm64" is specified, macOS Arm64 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"
  • "mac64arm"
  • "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
  |       |   +-- mac64arm
  |       |       +-- 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.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (119)

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.

Miru.PageTesting.Chrome

Package Description

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 (44)

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

Repository Stars
Sonarr/Sonarr
Smart PVR for newsgroup and bittorrent users.
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.
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.
testcontainers/testcontainers-dotnet
A library to support tests with throwaway instances of Docker containers for all compatible .NET Standard versions.
Version Downloads Last updated
114.0.5735.1600 0 5/30/2023
114.0.5735.1600-beta 1,637 5/4/2023
113.0.5672.6300 179,028 5/3/2023
113.0.5672.2400 12,731 5/3/2023
113.0.5672.2400-beta 2,541 4/10/2023
112.0.5615.4900 339,565 4/5/2023
112.0.5615.2800-beta 3,166 3/16/2023
111.0.5563.6400 463,219 3/8/2023
111.0.5563.4100 40,252 3/8/2023
111.0.5563.4100-beta 1,252 2/27/2023
111.0.5563.1900-beta 1,797 2/10/2023
110.0.5481.7700 468,710 2/8/2023
110.0.5481.3000 32,009 2/7/2023
110.0.5481.3000-beta 2,411 1/14/2023
109.0.5414.7400 603,732 1/11/2023
109.0.5414.2500-beta 3,487 12/2/2022
108.0.5359.7100 589,891 11/30/2022
108.0.5359.2200 48,484 11/29/2022
108.0.5359.2200-beta 1,818 11/3/2022
107.0.5304.6200 788,238 10/25/2022
107.0.5304.1800-beta 1,472 10/2/2022
106.0.5249.6100 512,701 9/28/2022
106.0.5249.2100 31,593 9/27/2022
106.0.5249.2100-beta 2,748 9/2/2022
105.0.5195.5200 658,346 8/31/2022
105.0.5195.1900 43,206 8/31/2022
105.0.5195.1900-beta 2,912 8/8/2022
104.0.5112.7900 549,736 8/3/2022
104.0.5112.2900 28,685 8/3/2022
104.0.5112.2900-beta 6,417 7/7/2022
104.0.5112.2000-beta 18,253 6/24/2022
103.0.5060.13400 194,735 7/20/2022
103.0.5060.5300 525,706 6/22/2022
103.0.5060.2400-beta 3,079 5/30/2022
102.0.5005.6102 610,690 5/28/2022
102.0.5005.6101 7,605 5/28/2022
102.0.5005.6100 87,004 5/25/2022
102.0.5005.2700 45,427 5/24/2022
102.0.5005.2700-beta 4,049 5/2/2022
101.0.4951.4100 556,968 4/27/2022
101.0.4951.1500-beta 4,355 4/2/2022
100.0.4896.6000 904,539 3/30/2022
100.0.4896.2000 41,922 3/30/2022
100.0.4896.2000-beta 3,367 3/4/2022
99.0.4844.5100 620,512 3/4/2022
99.0.4844.5100-beta 106,910 3/2/2022
99.0.4844.3500-beta 2,789 2/17/2022
99.0.4844.1700-beta 1,666 2/5/2022
98.0.4758.10200 336,691 2/15/2022
98.0.4758.8000 297,958 2/4/2022
98.0.4758.4800 102,888 2/3/2022
98.0.4758.4800-beta 44,443 1/12/2022
97.0.4692.7100 576,273 1/6/2022
97.0.4692.3600-beta 7,475 12/3/2021
97.0.4692.2000-beta 6,502 11/19/2021
96.0.4664.4500 1,196,596 11/16/2021
96.0.4664.3500-beta 5,944 11/8/2021
96.0.4664.1800-beta.2 824 11/3/2021
96.0.4664.1800-beta 2,192 10/25/2021
95.0.4638.6900 181,048 11/8/2021
95.0.4638.5401 132,478 11/3/2021
95.0.4638.5400 106,774 10/28/2021
95.0.4638.1700 204,796 10/20/2021
95.0.4638.1700-beta 16,543 9/28/2021
95.0.4638.1000-beta 1,904 9/21/2021
94.0.4606.11300 22,250 11/8/2021
94.0.4606.6100 615,595 9/28/2021
94.0.4606.4101 156,268 9/22/2021
94.0.4606.4101-beta 2,573 9/10/2021
93.0.4577.6300 168,367 9/14/2021
93.0.4577.1500 340,699 9/1/2021
93.0.4577.1500-beta 9,817 7/29/2021
92.0.4515.10700 653,185 7/29/2021
92.0.4515.4300 210,011 7/21/2021
92.0.4515.4300-beta 7,179 6/12/2021
91.0.4472.10100 637,351 6/12/2021
91.0.4472.1900 497,537 5/26/2021
91.0.4472.1900-beta 5,119 4/23/2021
90.0.4430.2400 982,204 4/14/2021
90.0.4430.2400-beta 6,857 3/16/2021
89.0.4389.2300 991,512 3/4/2021
89.0.4389.2300-beta 8,525 1/29/2021
88.0.4324.9600 911,444 1/21/2021
88.0.4324.2700 61,272 1/19/2021
88.0.4324.2700-beta 3,718 12/4/2020
87.0.4280.8800 1,190,307 12/2/2020
87.0.4280.2000 473,366 11/18/2020
87.0.4280.2000-beta 27,069 10/17/2020
86.0.4240.2200 705,007 10/9/2020
86.0.4240.2200-beta 15,996 9/4/2020
85.0.4183.8700 1,032,896 8/28/2020
85.0.4183.8300 183,154 8/26/2020
85.0.4183.3800-beta 5,487 7/24/2020
84.0.4147.3001 462,755 7/15/2020
84.0.4147.3001-beta 747 7/12/2020
84.0.4147.3000-beta 10,056 5/29/2020
83.0.4103.3915 45,636 7/15/2020
83.0.4103.3915-beta 4,809 7/11/2020
83.0.4103.3910 203,817 6/28/2020
83.0.4103.3910-beta 10,428 5/24/2020
83.0.4103.3900 998,379 5/20/2020
83.0.4103.3900-beta 16,539 5/6/2020
83.0.4103.1400-beta 5,823 4/17/2020
81.0.4044.13800 148,183 5/6/2020
81.0.4044.6900 345,701 4/9/2020
81.0.4044.6900-beta 2,094 3/18/2020
81.0.4044.2000-beta 4,095 2/14/2020
80.0.3987.10600 951,117 2/14/2020
80.0.3987.1600 262,482 2/5/2020
80.0.3987.1600-beta 3,284 12/20/2019
79.0.3945.3600 866,141 12/12/2019
79.0.3945.3600-beta 18,119 11/19/2019
79.0.3945.1600-beta 1,754 10/31/2019
78.0.3904.10500 342,652 11/19/2019
78.0.3904.7000 490,153 10/23/2019
78.0.3904.1100-beta 4,091 9/13/2019
77.0.3865.4000 541,768 9/13/2019
77.0.3865.4000-beta 2,614 8/21/2019
77.0.3865.10-beta 7,427 8/7/2019
76.0.3809.12600 270,131 8/22/2019
76.0.3809.6801 100,240 8/12/2019
76.0.3809.68 167,595 8/5/2019
76.0.3809.68-beta 5,059 7/17/2019
76.0.3809.25-beta 3,677 6/14/2019
76.0.3809.12-beta 838 6/8/2019
75.0.3770.140 322,241 7/14/2019
75.0.3770.90 217,841 6/14/2019
75.0.3770.8 63,064 6/8/2019
74.0.3729.6 486,910 4/25/2019
73.0.3683.68 304,485 3/13/2019
72.0.3626.69 444,559 3/5/2019
71.0.3578.137 44,583 3/5/2019
2.46.0 362,558 2/2/2019
2.45.0 419,976 12/11/2018
2.44.0 426,815 11/21/2018
2.43.0 877,008 10/18/2018
2.42.0.1 395,202 9/14/2018
2.41.0 570,108 7/28/2018
2.40.0 789,602 6/8/2018
2.39.0 98,160 5/30/2018
2.38.0.1 467,004 4/26/2018
2.38.0 559,296 4/18/2018
2.37.0 619,694 3/17/2018
2.36.0 251,931 3/2/2018
2.35.0 463,673 1/11/2018
2.34.0 132,195 12/10/2017
2.33.0 490,151 10/4/2017
2.32.0 162,496 8/31/2017
2.31.0 134,593 7/23/2017
2.30.0.1 467,715 6/8/2017
2.29.0 349,553 4/4/2017
2.28.0.2-beta 2,115 3/21/2017
2.28.0.1-beta 3,245 3/9/2017
2.28.0 120,923 3/9/2017
2.27.0.7-beta 2,360 3/3/2017
2.27.0.6-beta 869 3/2/2017
2.27.0.2-beta 1,088 2/28/2017
2.27.0 266,762 12/22/2016
2.26.0 59,017 12/6/2016
2.25.0.8 125,077 11/15/2016
2.25.0.8-beta 5,462 10/29/2016
2.25.0 99,348 10/24/2016
2.24.0 141,287 9/16/2016
2.23.0.1 106,681 8/10/2016
2.23.0 4,185 8/9/2016
2.22.0 111,721 6/8/2016
2.21.0.1-beta 2,681 5/5/2016
2.21.0 212,491 1/26/2016
2.20.0 165,552 10/9/2015
2.19.0 44,605 9/6/2015
2.18.0 11,042 8/22/2015
2.17.0 8,605 8/12/2015
2.16.0 16,937 6/27/2015
2.15.0 40,919 4/1/2015
2.14.0.1-beta 1,115 3/6/2015
2.14.0 19,918 3/3/2015
2.13.0 18,829 1/6/2015
2.12.0 19,616 10/30/2014
2.10.0.1-beta2 2,019 8/14/2014
2.10.0.1-beta 966 8/14/2014
2.10.0 30,054 5/8/2014
2.9.0.1 6,033 4/7/2014
2.9.0.1-beta3 1,092 4/5/2014
2.9.0.1-beta2 1,081 4/3/2014
2.9.0 9,727 3/27/2014
2.8.0 12,514 1/24/2014
2.3.0 8,487 9/7/2013
2.2.0 8,300 8/28/2013

114.0.5735.1600
     - Chrome Driver 114.0.5735.16 release

     To see all the change logs, please visit the following URL.
     - https://github.com/jsakamoto/nupkg-selenium-webdriver-chromedriver/blob/master/RELEASE-NOTES.txt