Selenium.WebDriver.ChromeDriver 103.0.5060.5300

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

// Install Selenium.WebDriver.ChromeDriver as a Cake Tool
#tool nuget:?package=Selenium.WebDriver.ChromeDriver&version=103.0.5060.5300
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, macOS M1, 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 103:

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

If you are using Chrome version 102:

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

If you are using Chrome version 101:

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

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

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 (>=103) 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.

Miru.PageTesting.Chrome

Package Description

GitHub repositories (34)

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.
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.
aspnet/KestrelHttpServer
[Archived] A cross platform web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore
Lidarr/Lidarr
Looks and smells like Sonarr but made for music.
Version Downloads Last updated
104.0.5112.2000-beta 1,508 6/24/2022
103.0.5060.5300 69,974 6/22/2022
103.0.5060.2400-beta 2,466 5/30/2022
102.0.5005.6102 249,465 5/28/2022
102.0.5005.6101 4,716 5/28/2022
102.0.5005.6100 45,255 5/25/2022
102.0.5005.2700 33,101 5/24/2022
102.0.5005.2700-beta 2,886 5/2/2022
101.0.4951.4100 403,086 4/27/2022
101.0.4951.1500-beta 3,903 4/2/2022
100.0.4896.6000 526,371 3/30/2022
100.0.4896.2000 32,046 3/30/2022
100.0.4896.2000-beta 3,023 3/4/2022
99.0.4844.5100 389,285 3/4/2022
99.0.4844.5100-beta 31,380 3/2/2022
99.0.4844.3500-beta 1,658 2/17/2022
99.0.4844.1700-beta 1,506 2/5/2022
98.0.4758.10200 252,441 2/15/2022
98.0.4758.8000 263,741 2/4/2022
98.0.4758.4800 77,288 2/3/2022
98.0.4758.4800-beta 42,590 1/12/2022
97.0.4692.7100 434,335 1/6/2022
97.0.4692.3600-beta 7,262 12/3/2021
97.0.4692.2000-beta 6,359 11/19/2021
96.0.4664.4500 900,384 11/16/2021
96.0.4664.3500-beta 5,620 11/8/2021
96.0.4664.1800-beta.2 497 11/3/2021
96.0.4664.1800-beta 2,092 10/25/2021
95.0.4638.6900 156,261 11/8/2021
95.0.4638.5401 100,834 11/3/2021
95.0.4638.5400 96,036 10/28/2021
95.0.4638.1700 189,417 10/20/2021
95.0.4638.1700-beta 12,506 9/28/2021
95.0.4638.1000-beta 1,837 9/21/2021
94.0.4606.11300 8,995 11/8/2021
94.0.4606.6100 515,639 9/28/2021
94.0.4606.4101 141,815 9/22/2021
94.0.4606.4101-beta 2,502 9/10/2021
93.0.4577.6300 134,270 9/14/2021
93.0.4577.1500 284,319 9/1/2021
93.0.4577.1500-beta 9,559 7/29/2021
92.0.4515.10700 554,098 7/29/2021
92.0.4515.4300 192,877 7/21/2021
92.0.4515.4300-beta 6,138 6/12/2021
91.0.4472.10100 518,463 6/12/2021
91.0.4472.1900 439,957 5/26/2021
91.0.4472.1900-beta 4,918 4/23/2021
90.0.4430.2400 864,403 4/14/2021
90.0.4430.2400-beta 6,295 3/16/2021
89.0.4389.2300 906,560 3/4/2021
89.0.4389.2300-beta 7,762 1/29/2021
88.0.4324.9600 752,015 1/21/2021
88.0.4324.2700 50,215 1/19/2021
88.0.4324.2700-beta 3,614 12/4/2020
87.0.4280.8800 1,120,812 12/2/2020
87.0.4280.2000 406,502 11/18/2020
87.0.4280.2000-beta 26,921 10/17/2020
86.0.4240.2200 639,491 10/9/2020
86.0.4240.2200-beta 15,537 9/4/2020
85.0.4183.8700 933,452 8/28/2020
85.0.4183.8300 175,026 8/26/2020
85.0.4183.3800-beta 5,249 7/24/2020
84.0.4147.3001 405,294 7/15/2020
84.0.4147.3001-beta 691 7/12/2020
84.0.4147.3000-beta 8,645 5/29/2020
83.0.4103.3915 38,092 7/15/2020
83.0.4103.3915-beta 2,847 7/11/2020
83.0.4103.3910 192,379 6/28/2020
83.0.4103.3910-beta 8,719 5/24/2020
83.0.4103.3900 934,166 5/20/2020
83.0.4103.3900-beta 16,449 5/6/2020
83.0.4103.1400-beta 5,664 4/17/2020
81.0.4044.13800 135,604 5/6/2020
81.0.4044.6900 315,057 4/9/2020
81.0.4044.6900-beta 2,052 3/18/2020
81.0.4044.2000-beta 3,849 2/14/2020
80.0.3987.10600 850,750 2/14/2020
80.0.3987.1600 258,253 2/5/2020
80.0.3987.1600-beta 3,186 12/20/2019
79.0.3945.3600 816,209 12/12/2019
79.0.3945.3600-beta 18,020 11/19/2019
79.0.3945.1600-beta 1,701 10/31/2019
78.0.3904.10500 313,392 11/19/2019
78.0.3904.7000 466,820 10/23/2019
78.0.3904.1100-beta 4,030 9/13/2019
77.0.3865.4000 481,722 9/13/2019
77.0.3865.4000-beta 2,553 8/21/2019
77.0.3865.10-beta 6,611 8/7/2019
76.0.3809.12600 252,075 8/22/2019
76.0.3809.6801 96,249 8/12/2019
76.0.3809.68 152,464 8/5/2019
76.0.3809.68-beta 4,997 7/17/2019
76.0.3809.25-beta 3,606 6/14/2019
76.0.3809.12-beta 780 6/8/2019
75.0.3770.140 293,171 7/14/2019
75.0.3770.90 210,080 6/14/2019
75.0.3770.8 60,510 6/8/2019
74.0.3729.6 451,661 4/25/2019
73.0.3683.68 282,495 3/13/2019
72.0.3626.69 391,732 3/5/2019
71.0.3578.137 40,592 3/5/2019
2.46.0 351,063 2/2/2019
2.45.0 367,902 12/11/2018
2.44.0 361,669 11/21/2018
2.43.0 844,521 10/18/2018
2.42.0.1 371,345 9/14/2018
2.41.0 533,861 7/28/2018
2.40.0 751,821 6/8/2018
2.39.0 94,189 5/30/2018
2.38.0.1 427,201 4/26/2018
2.38.0 457,353 4/18/2018
2.37.0 597,798 3/17/2018
2.36.0 244,423 3/2/2018
2.35.0 447,864 1/11/2018
2.34.0 127,082 12/10/2017
2.33.0 463,340 10/4/2017
2.32.0 152,197 8/31/2017
2.31.0 125,950 7/23/2017
2.30.0.1 432,604 6/8/2017
2.29.0 343,403 4/4/2017
2.28.0.2-beta 2,038 3/21/2017
2.28.0.1-beta 3,170 3/9/2017
2.28.0 113,163 3/9/2017
2.27.0.7-beta 2,296 3/3/2017
2.27.0.6-beta 806 3/2/2017
2.27.0.2-beta 1,020 2/28/2017
2.27.0 252,063 12/22/2016
2.26.0 56,305 12/6/2016
2.25.0.8 117,036 11/15/2016
2.25.0.8-beta 5,129 10/29/2016
2.25.0 95,049 10/24/2016
2.24.0 132,154 9/16/2016
2.23.0.1 102,242 8/10/2016
2.23.0 3,976 8/9/2016
2.22.0 101,544 6/8/2016
2.21.0.1-beta 2,617 5/5/2016
2.21.0 201,741 1/26/2016
2.20.0 158,051 10/9/2015
2.19.0 43,338 9/6/2015
2.18.0 10,628 8/22/2015
2.17.0 8,253 8/12/2015
2.16.0 16,229 6/27/2015
2.15.0 39,573 4/1/2015
2.14.0.1-beta 1,047 3/6/2015
2.14.0 18,914 3/3/2015
2.13.0 18,066 1/6/2015
2.12.0 18,680 10/30/2014
2.10.0.1-beta2 1,953 8/14/2014
2.10.0.1-beta 869 8/14/2014
2.10.0 28,402 5/8/2014
2.9.0.1 5,755 4/7/2014
2.9.0.1-beta3 991 4/5/2014
2.9.0.1-beta2 981 4/3/2014
2.9.0 9,459 3/27/2014
2.8.0 10,517 1/24/2014
2.3.0 8,188 9/7/2013
2.2.0 6,723 8/28/2013

103.0.5060.5300
     - Chrome Driver 103.0.5060.53 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