Selenium.WebDriver.ChromeDriver 2.38.0.1

Install Chrome Driver (Win32, macOS, and Linux64) for Selenium WebDriver into your Unit Test Project.
     "chromedriver(.exe)" is copied to bin folder from package folder when the build process.
     NuGet package restoring ready, and no need to commit "chromedriver(.exe)" binary into source code control repository.
     / Selenium WebDriver用 Chrome Driver (Win32, macOS, 及び Linux64) を単体テストプロジェクトに追加します。
     "chromedriver(.exe)" はビルド時にパッケージフォルダから bin フォルダへコピーされます。
     NuGet パッケージの復元に対応済み、"chromedriver(.exe)" をソース管理リポジトリに登録する必要はありません。
     / 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.

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

NuGet package - Selenium WebDriver ChromeDriver

NuGet Package

What's this? / これは何?

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

この NuGet パッケージは、Selenium WebDriver用 Chrome Driver (Win32, macOS, 及び Linux64) を単体テストプロジェクトに追加します。

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

"chromedriver(.exe)" はソリューションエクスプローラ上には現れませんが、ビルド時にパッケージフォルダから bin フォルダへコピーされます。

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

NuGet パッケージの復元に対応済み、"chromedriver(.exe)" をソース管理リポジトリに登録する必要はありません。

How to install? / インストール方法

For example, at the package manager console on Visual Studio, enter following command.
一例として、Visual Studio 上のパッケージ管理コンソールにて、下記のコマンドを入力してください。

PM> Install-Package Selenium.WebDriver.ChromeDriver

Detail / 詳細

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 output folder during build process.

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.

"chromedriver(.exe)" は、既定の構成では、発行ファイルに含まれません。この挙動は仕様です。

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

"chromedriver(.exe)" を発行ファイルに含めるには、コンパイル定数 _PUBLISH_CHROMEDRIVER を定義してください。

define _PUBLISH_CHROMEDRIVER compilation symbol

Anoter 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.

別の方法として、コンパイル定数を定義する代わりに、MSBuild ファイル (.csproj, .vbproj, etc...) 中で PublishChromeDriver プロパティを値 true で定義することでドライバーを発行ファイルに含めることができます。

  <Project ...>
    ...
    <PropertyGroup>
      ...
      <PublishChromeDriver>true</PublishChromeDriver>
      ...
    </PropertyGroup>
...
</Project>
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.

PublishChromeDriver MSBuild プロパティは常に _PUBLISH_CHROMEDRIVER コンパイル定数を定義しているか否かの条件を上書きします。もし PublishChromeDriver MSBuild プロパティを false で定義したならば、_PUBLISH_CHROMEDRIVER コンパイル定数を定義しているか否かによらず、ドライバは発行ファイルに含められません。

NuGet package - Selenium WebDriver ChromeDriver

NuGet Package

What's this? / これは何?

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

この NuGet パッケージは、Selenium WebDriver用 Chrome Driver (Win32, macOS, 及び Linux64) を単体テストプロジェクトに追加します。

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

"chromedriver(.exe)" はソリューションエクスプローラ上には現れませんが、ビルド時にパッケージフォルダから bin フォルダへコピーされます。

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

NuGet パッケージの復元に対応済み、"chromedriver(.exe)" をソース管理リポジトリに登録する必要はありません。

How to install? / インストール方法

For example, at the package manager console on Visual Studio, enter following command.
一例として、Visual Studio 上のパッケージ管理コンソールにて、下記のコマンドを入力してください。

PM> Install-Package Selenium.WebDriver.ChromeDriver

Detail / 詳細

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 output folder during build process.

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.

"chromedriver(.exe)" は、既定の構成では、発行ファイルに含まれません。この挙動は仕様です。

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

"chromedriver(.exe)" を発行ファイルに含めるには、コンパイル定数 _PUBLISH_CHROMEDRIVER を定義してください。

define _PUBLISH_CHROMEDRIVER compilation symbol

Anoter 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.

別の方法として、コンパイル定数を定義する代わりに、MSBuild ファイル (.csproj, .vbproj, etc...) 中で PublishChromeDriver プロパティを値 true で定義することでドライバーを発行ファイルに含めることができます。

  <Project ...>
    ...
    <PropertyGroup>
      ...
      <PublishChromeDriver>true</PublishChromeDriver>
      ...
    </PropertyGroup>
...
</Project>
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.

PublishChromeDriver MSBuild プロパティは常に _PUBLISH_CHROMEDRIVER コンパイル定数を定義しているか否かの条件を上書きします。もし PublishChromeDriver MSBuild プロパティを false で定義したならば、_PUBLISH_CHROMEDRIVER コンパイル定数を定義しているか否かによらず、ドライバは発行ファイルに含められません。

Release Notes

v.2.38.0.1
     - Chrome Driver 2.38 Build 552518+ release
   v.2.38.0.0
     - Chrome Driver 2.38 release
   v.2.37.0.0
     - Chrome Driver 2.37 release
   v.2.36.0.0
     - Chrome Driver 2.36 release
   v.2.35.0.0
     - Chrome Driver 2.35 release
   v.2.34.0.0
     - Chrome Driver 2.34 release
   v.2.33.0.0
     - Chrome Driver 2.33 release
   v.2.32.0.0
     - Chrome Driver 2.32 release
   v.2.31.0.0
     - Chrome Driver 2.31 release
   v.2.30.0.0
     - Chrome Driver 2.30 release
   v.2.29.0.0
     - Chrome Driver 2.29 release
   v.2.28.0.2
     - add support for Mono on Linux
   v.2.28.0.1
     - add support for macOS and Xamarin Studio
   v.2.28.0.0
     - Chrome Driver 2.28 release
   v.2.27.0.0
     - Chrome Driver 2.27 release
   v.2.26.0.0
     - Chrome Driver 2.26 release
   v.2.25.0.8
     - Add support for "clean" MSBuild task.
     - Add support for publishing driver file when "_PUBLISH_CHROMEDRIVE" compilation symbol is defined.
   v.2.25.0.0
     - Chrome Driver 2.25 release
     v.2.24.0.0
     - Chrome Driver 2.24 release
     v.2.23.0.1
     - Fix: cause build error when specified absolute output path.
     v.2.23.0.0
     - Chrome Driver 2.23 release
   v.2.22.0.0
     - Chrome Driver 2.22 release
   v.2.21.0.1
   - Change: Implement copy driver task as MSBuild script, and remove install/uninstall PwoerShell scripts.
   v.2.21.0.0
     - Chrome Driver 2.21 release
   v.2.20.0.0
     - Chrome Driver 2.20 release
     v.2.19.0.0
     - Chrome Driver 2.19 release
     v.2.18.0.0
     - Chrome Driver 2.18 release
     v.2.17.0.0
     - Chrome Driver 2.17 release
     v.2.16.0.0
     - Chrome Driver 2.16 release
     v.2.15.0.0
     - Chrome Driver 2.15 release
     v.2.14.0.1
     - Include chromedriver.exe in this package, no downloading during package instllation.
     v.2.14.0.0
     - Chrome Driver 2.14 release
     v.2.13.0.0
     - Chrome Driver 2.13 release
     v.2.12.0.0
     - Chrome Driver 2.12 release
     v.2.10.0.1
     - Fix: Installing this package was fail when .csproj file and packages folder are in a same folder.
     v.2.10
     - Chrome Driver 2.10 release
     v.2.9.0.1
     - HTTP proxy settings are available now.(1. HTTP_PROXY environment variable, 2. NuGet configuration)
     - Fix: Occur exception at Add-Type in init.ps1 when installing the package.

Dependencies

This package has no dependencies.

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

Repository Stars
aspnet/KestrelHttpServer
[Archived] A cross platform web server for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore
jakubgarfield/Bonobo-Git-Server
Bonobo Git Server for Windows is a web application you can install on your IIS and easily manage and connect to your git repositories. Go to homepage for release and more info.
HTBox/allReady
This repo contains the code for allReady, an open-source solution focused on increasing awareness, efficiency and impact of preparedness campaigns as they are delivered by humanitarian and disaster response organizations in local communities.
Lunat1q/Catchem-PoGo
Project is DEAD, Discord server: https://discord.me/Catchem
featurist/coypu
Intuitive, robust browser automation for .Net
AutomateThePlanet/AutomateThePlanet-Learning-Series
Automate The Planet Series Source Code
Necrobot-Private/NecroBot
NecroBot2
Inumedia/SlackAPI
.NET Implementation of the Slack team communication platform API.
atata-framework/atata
C#/.NET test automation framework for web
Warewolf-ESB/Warewolf
Effortless Microservice Design and Integration. This repository includes the code-base for the Warewolf Studio and Server.

Version History

Version Downloads Last updated
78.0.3904.1100-beta 1,442 9/13/2019
77.0.3865.4000 80,108 9/13/2019
77.0.3865.4000-beta 1,602 8/21/2019
77.0.3865.10-beta 764 8/7/2019
76.0.3809.12600 92,602 8/22/2019
76.0.3809.6801 51,352 8/12/2019
76.0.3809.68 67,182 8/5/2019
76.0.3809.68-beta 4,260 7/17/2019
76.0.3809.25-beta 2,160 6/14/2019
76.0.3809.12-beta 389 6/8/2019
75.0.3770.140 101,281 7/14/2019
75.0.3770.90 113,078 6/14/2019
75.0.3770.8 38,168 6/8/2019
74.0.3729.6 298,446 4/25/2019
73.0.3683.68 167,105 3/13/2019
72.0.3626.69 129,401 3/5/2019
71.0.3578.137 13,852 3/5/2019
2.46.0 206,985 2/2/2019
2.45.0 191,572 12/11/2018
2.44.0 172,706 11/21/2018
2.43.0 388,977 10/18/2018
2.42.0.1 204,311 9/14/2018
2.41.0 376,074 7/28/2018
2.40.0 424,601 6/8/2018
2.39.0 70,315 5/30/2018
2.38.0.1 288,534 4/26/2018
2.38.0 152,682 4/18/2018
2.37.0 429,806 3/17/2018
2.36.0 199,908 3/2/2018
2.35.0 336,556 1/11/2018
2.34.0 96,901 12/10/2017
2.33.0 363,589 10/4/2017
2.32.0 120,314 8/31/2017
2.31.0 91,867 7/23/2017
2.30.0.1 201,395 6/8/2017
2.29.0 268,805 4/4/2017
2.28.0.2-beta 1,543 3/21/2017
2.28.0.1-beta 2,694 3/9/2017
2.28.0 96,390 3/9/2017
2.27.0.7-beta 1,838 3/3/2017
2.27.0.6-beta 335 3/2/2017
2.27.0.2-beta 562 2/28/2017
2.27.0 205,714 12/22/2016
2.26.0 46,133 12/6/2016
2.25.0.8 83,988 11/15/2016
2.25.0.8-beta 3,440 10/29/2016
2.25.0 80,904 10/24/2016
2.24.0 91,180 9/16/2016
2.23.0.1 91,411 8/10/2016
2.23.0 3,328 8/9/2016
2.22.0 79,957 6/8/2016
2.21.0.1-beta 2,148 5/5/2016
2.21.0 166,860 1/26/2016
2.20.0 139,633 10/9/2015
2.19.0 29,262 9/6/2015
2.18.0 9,457 8/22/2015
2.17.0 6,685 8/12/2015
2.16.0 13,273 6/27/2015
2.15.0 26,725 4/1/2015
2.14.0.1-beta 569 3/6/2015
2.14.0 13,496 3/3/2015
2.13.0 13,812 1/6/2015
2.12.0 16,816 10/30/2014
2.10.0.1-beta2 1,455 8/14/2014
2.10.0.1-beta 378 8/14/2014
2.10.0 23,046 5/8/2014
2.9.0.1 4,930 4/7/2014
2.9.0.1-beta3 391 4/5/2014
2.9.0.1-beta2 382 4/3/2014
2.9.0 7,200 3/27/2014
2.8.0 6,943 1/24/2014
2.3.0 7,350 9/7/2013
2.2.0 2,056 8/28/2013
Show less