Selenium.WebDriver.ChromeDriver 2.38.0.1

Selenium.WebDriver.ChromeDriver (Win32, macOS, and Linux64)

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

Version History

Version Downloads Last updated
2.45.0 2,979 12/11/2018
2.44.0 26,245 11/21/2018
2.43.0 84,716 10/18/2018
2.42.0.1 78,879 9/14/2018
2.41.0 200,719 7/28/2018
2.40.0 215,415 6/8/2018
2.39.0 44,393 5/30/2018
2.38.0.1 190,262 4/26/2018
2.38.0 110,878 4/18/2018
2.37.0 300,426 3/17/2018
2.36.0 157,965 3/2/2018
2.35.0 270,085 1/11/2018
2.34.0 77,031 12/10/2017
2.33.0 326,564 10/4/2017
2.32.0 98,861 8/31/2017
2.31.0 80,417 7/23/2017
2.30.0.1 181,060 6/8/2017
2.29.0 232,956 4/4/2017
2.28.0.2-beta 1,410 3/21/2017
2.28.0.1-beta 2,552 3/9/2017
2.28.0 90,901 3/9/2017
2.27.0.7-beta 1,708 3/3/2017
2.27.0.6-beta 193 3/2/2017
2.27.0.2-beta 431 2/28/2017
2.27.0 192,465 12/22/2016
2.26.0 40,813 12/6/2016
2.25.0.8 69,481 11/15/2016
2.25.0.8-beta 2,991 10/29/2016
2.25.0 77,033 10/24/2016
2.24.0 82,906 9/16/2016
2.23.0.1 79,802 8/10/2016
2.23.0 1,632 8/9/2016
2.22.0 65,523 6/8/2016
2.21.0.1-beta 1,995 5/5/2016
2.21.0 113,034 1/26/2016
2.20.0 129,499 10/9/2015
2.19.0 21,957 9/6/2015
2.18.0 8,875 8/22/2015
2.17.0 6,013 8/12/2015
2.16.0 11,352 6/27/2015
2.15.0 21,754 4/1/2015
2.14.0.1-beta 425 3/6/2015
2.14.0 12,501 3/3/2015
2.13.0 13,255 1/6/2015
2.12.0 16,574 10/30/2014
2.10.0.1-beta2 1,327 8/14/2014
2.10.0.1-beta 247 8/14/2014
2.10.0 21,398 5/8/2014
2.9.0.1 4,562 4/7/2014
2.9.0.1-beta3 258 4/5/2014
2.9.0.1-beta2 247 4/3/2014
2.9.0 5,170 3/27/2014
2.8.0 6,465 1/24/2014
2.3.0 7,082 9/7/2013
2.2.0 1,345 8/28/2013
Show less