Selenium.WebDriver.MSEdgeDriver.win32
131.0.2903.48
dotnet add package Selenium.WebDriver.MSEdgeDriver.win32 --version 131.0.2903.48
NuGet\Install-Package Selenium.WebDriver.MSEdgeDriver.win32 -Version 131.0.2903.48
<PackageReference Include="Selenium.WebDriver.MSEdgeDriver.win32" Version="131.0.2903.48" />
paket add Selenium.WebDriver.MSEdgeDriver.win32 --version 131.0.2903.48
#r "nuget: Selenium.WebDriver.MSEdgeDriver.win32, 131.0.2903.48"
// Install Selenium.WebDriver.MSEdgeDriver.win32 as a Cake Addin #addin nuget:?package=Selenium.WebDriver.MSEdgeDriver.win32&version=131.0.2903.48 // Install Selenium.WebDriver.MSEdgeDriver.win32 as a Cake Tool #tool nuget:?package=Selenium.WebDriver.MSEdgeDriver.win32&version=131.0.2903.48
DISCLAIMER: Maybe this package is not for you
From v4.0, Selenium has Selenium Manager (https://www.selenium.dev/documentation/selenium_manager/):
Selenium Manager is a command-line tool implemented in Rust that provides automated driver and browser management for Selenium. Selenium bindings use this tool by default, so you do not need to download it or add anything to your code or do anything else to use it
Install the NuGet Package
Install-Package Selenium.WebDriver.MSEdgeDriver
or
dotnet add package Selenium.WebDriver.MSEdgeDriver
Getting started
var edgeOptions = new EdgeOptions
{
UseChromium = true
};
var edgeDriverService = EdgeDriverService.CreateChromiumService();
For more information, see https://github.com/microsoft/edge-selenium-tools.
Create the NuGet package
getPackage.bat <version>
For example, to automatically download the Microsoft Edge Driver and create the NuGet package '.\dist\Selenium.WebDriver.MSEdgeDriver.84.0.522.49.nupkg':
getPackage.bat 84.0.522.49
Contributing
Most the process is automated, but I still need to check MS Edge Driver's page and execute the batch file manually. I am trying to do this once a month. If you would like to have faster releases, please contact me to become a contributor.
Cross-platform building and publishing
Edge driver developers normally releases versions with win32, win64, mac and linux binaries, but sometimes they decide to release one version with just linux, or just mac and windows binaries. The automated process can only make nuget packages of full releases.
How to include the driver file into published files?
"msedgedriver(.exe)" isn't included in published files on default configuration. This behavior is by design and follows https://raw.githubusercontent.com/jsakamoto/nupkg-selenium-webdriver-chromedriver/ design. For more info reffer to guides at https://raw.githubusercontent.com/jsakamoto/nupkg-selenium-webdriver-chromedriver.
To include published files, define PublishMsEdgeDriver
property with value is "true" in MSBuild file (.csproj, .vbproj, etc...) to publish the driver file instead of define compilation symbol.
<Project ...>
...
<PropertyGroup>
...
<PublishMsEdgeDriver>true</PublishMsEdgeDriver>
...
</PropertyGroup>
...
</Project>
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
131.0.2903.48 | 915 | 11/15/2024 |
130.0.2849.46 | 1,639 | 10/22/2024 |
129.0.2792.52 | 1,889 | 9/23/2024 |
128.0.2739.54 | 4,201 | 9/2/2024 |
128.0.2739.42 | 1,213 | 8/26/2024 |
127.0.2651.105 | 424 | 8/16/2024 |
127.0.2651.74 | 202 | 7/30/2024 |
126.0.2592.61 | 528 | 6/18/2024 |
125.0.2535.92 | 220 | 6/13/2024 |
125.0.2535.51 | 1,023 | 5/21/2024 |
124.0.2478.80 | 2,871 | 5/6/2024 |
123.0.2420.65 | 3,662 | 4/1/2024 |
122.0.2365.59 | 4,497 | 2/28/2024 |
121.0.2277.128 | 3,132 | 2/19/2024 |
121.0.2277.83 | 455 | 1/30/2024 |
120.0.2210.61 | 396 | 12/12/2023 |
119.0.2151.72 | 1,041 | 11/20/2023 |
119.0.2151.44 | 317 | 11/3/2023 |
118.0.2088.61 | 232 | 10/23/2023 |
117.0.2045.30 | 374 | 9/19/2023 |
116.0.1938.76 | 1,150 | 9/19/2023 |
115.0.1901.200 | 319 | 9/19/2023 |