Selenium.WebDriver.IEDriver 4.14.0

dotnet add package Selenium.WebDriver.IEDriver --version 4.14.0
NuGet\Install-Package Selenium.WebDriver.IEDriver -Version 4.14.0
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.IEDriver" Version="4.14.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Selenium.WebDriver.IEDriver --version 4.14.0
#r "nuget: Selenium.WebDriver.IEDriver, 4.14.0"
#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.IEDriver as a Cake Addin
#addin nuget:?package=Selenium.WebDriver.IEDriver&version=4.14.0

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

NuGet package - Selenium WebDriver IEDriver

NuGet Package

What's this?

This NuGet package installs IE Driver(x86) for Selenium WebDriver into your Unit Test Project.

"IEDriverServer.exe" does not appear in Solution Explorer, but it is copied to the bin folder from the package folder during the build process.

This package is ready for NuGet package restoring, and no need to commit the "IEDriverServer.exe" binary into the 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, enter the following command at the package manager console on Visual Studio.

PM> Install-Package Selenium.WebDriver.IEDriver

Required Configuration

Before automation Internet Explorer (or IE mode in Microsoft Edge), you must set up some configurations as below:

  • You must set the "Protected Mode" settings for each zone to be the same value.
  • You also need to set "Change the size of text, apps, and other items" to 100% in display settings.

Please see also: 🌎"Required Configuration - IE Driver Server | Selenium"

Notice

The "Enable Protected Mode" check box no longer exists in the "Internet Properties" dialog of the control panel on Windows 11 or later because Internet Explorer as a standalone application is no longer supported on Windows 11.

To configure the "Protected Mode" settings for each zone on Windows 11, I recommend using "Local Group Policy Editor" with the following steps instead of using the "Internet Properties" dialog.

  1. Open the "Edit group policy" menu item from the Start menu.
  2. Then, the "Local Group Policy Editor" window will be opened.
  3. Expand the left tree from the root node "Local Computer Policy" to "Computer Configuration" > "Administrative Templates" > "Windows Components" > "Internet Explorer" > "Internet Control Panel" > "Security Page".
  4. You will see some sub-nodes that node name ends with "...Zone", and you should be able to see the "Turn on Protected Mode" setting item In each sub-node.
  5. Double click the "Turn on Protected Mode" setting item and select "Enable" or "Disable," which you want, and click the "OK" button to apply and close it.
  6. Do that for all of the "...Zone" sub-nodes.

Local Group Policy Editor

How to automate IE mode in Microsoft Edge?

To automate IE mode in Microsoft Edge (not Internet Explorer as a standalone application), you should have to configure the options for IE Driver like below:

using OpenQA.Selenium;
using OpenQA.Selenium.IE;

var ieOptions = new InternetExplorerOptions
{
    // These 3 lines are needed to use Microsoft Edge IE mode.
    AttachToEdgeChrome = true,
    EdgeExecutablePath = "C:/Program Files (x86)/Microsoft/Edge/Application/msedge.exe",
    IgnoreZoomLevel = true,
};

using var driver = new InternetExplorerDriver(ieOptions);
...

Please see also: 🌎"Use Internet Explorer Driver to automate IE mode in Microsoft Edge | Microsoft Docs"

How to include the driver file into published files?

"IEDriverServer.exe" isn't included in published files on the default configuration. This behavior is by design.

If you want to include "IEDriverServer.exe" into published files, please define the _PUBLISH_IEDRIVER compilation symbol.

define _PUBLISH_IEDRIVER compilation symbol

Another way, you can define PublishIEDriver property with value is "true" in the MSBuild file (.csproj, .vbproj, etc...) to publish the driver file instead of defining compilation symbol.

  <Project ...>
    ...
    <PropertyGroup>
      ...
      <PublishIEDriver>true</PublishIEDriver>
      ...
    </PropertyGroup>
...
</Project>

You can also define the PublishIEDriver property from the command line -p option for the dotnet publish command.

> dotnet publish -p:PublishChromeDriver=true

Note

PublishIEDriver MSBuild property always overrides the condition of defining the_PUBLISH_IEDRIVER compilation symbol or not. If you define PublishIEDriver MSBuild property with false, then the driver file isn't included in publish files whenever define _PUBLISH_IEDRIVER compilation symbol or not.

Appendix

Where is IEDriverServer.exe saved to?

IEDriverServer.exe exists at
" {solution folder} /packages/Selenium.WebDriver.IEDriver. {ver} /driver"
folder.

 {Solution folder}/
  +-- packages/
  |   +-- Selenium.WebDriver.IEDriver.{version}/
  |       +-- driver/
  |       |   +-- IEDriverServer.exe
  |       +-- build/
  +-- {project folder}/
      +-- bin/
          +-- Debug/
          |   +-- IEDriverServer.exe (copy from above by build process)
          +-- Release/
              +-- IEDriverServer.exe (copy from above by build process)

And package installer configures msbuild tasks such as .csproj to copy IEDriverServer.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 file of the IE Driver is licensed under the Apache License, Version 2.0.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (48)

Showing the top 5 NuGet packages that depend on Selenium.WebDriver.IEDriver:

Package Downloads
AutoToolKit

MzAutomation Test Framework. Documentation coming soon..

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

Animatronio

Selenium Framework

Objectivity.Test.Automation.Common.Features

[DEPRECATED] Use Install-Package Ocaramba.Features Install-Package Ocaramba.MsTest Install-Package Ocaramba.NUnit Install-Package Ocaramba.xUnit instead

GitHub repositories (10)

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

Repository Stars
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.
AutomateThePlanet/AutomateThePlanet-Learning-Series
Automate The Planet Series Source Code
featurist/coypu
Intuitive, robust browser automation for .Net
Implem/Implem.Pleasanter
Pleasanter is a no-code/low-code development platform that runs on .NET. You can quickly create business applications with simple operations.
Accenture/Ocaramba
C# Framework to automate tests using Selenium WebDriver
Version Downloads Last updated
4.14.0 69,649 10/11/2023
4.11.0 57,151 7/31/2023
4.10.0 89,009 6/7/2023
4.8.1 96,610 2/18/2023
4.8.0 25,565 1/23/2023
4.7.0 79,736 12/2/2022
4.6.0 26,056 11/4/2022
4.5.0 36,188 9/28/2022
4.3.0 118,907 8/9/2022
4.2.0 128,719 5/28/2022
4.0.0.1 99,938 3/22/2022
4.0.0 230,878 11/26/2021
3.150.1.2 1,765,637 7/15/2020
3.150.1.2-beta 2,930 7/12/2020
3.150.1.1 46,271 6/28/2020
3.150.1.1-beta 4,270 5/25/2020
3.150.1 1,435,602 10/18/2019
3.150.0 388,058 8/23/2019
3.141.59 514,336 4/11/2019
3.141.5 633,399 1/15/2019
3.141.0 409,462 11/1/2018
3.14.0 631,219 8/3/2018
3.13.0 222,372 6/26/2018
3.12.0 239,267 5/9/2018
3.11.1 366,736 3/14/2018
3.11.0 26,393 3/12/2018
3.10.0 53,208 3/3/2018
3.9.0 123,436 2/6/2018
3.8.0 309,957 12/2/2017
3.7.0 278,219 11/4/2017
3.6.0 144,115 9/26/2017
3.5.1 102,472 8/18/2017
3.5.0 27,626 8/11/2017
3.4.0 513,703 4/22/2017
3.3.0 132,659 3/8/2017
3.2.0 48,506 2/24/2017
3.1.0 39,792 2/17/2017
3.0.0.1 179,203 11/15/2016
3.0.0.1-beta 5,860 10/30/2016
3.0.0 62,124 10/14/2016
2.53.1.1 104,782 8/10/2016
2.53.1 18,095 8/10/2016
2.53.0.1-beta 8,577 5/5/2016
2.53.0 171,071 3/18/2016
2.52.2 6,613 3/15/2016
2.49.0 41,444 1/26/2016
2.48.0 64,139 10/8/2015
2.47.0 30,080 8/12/2015
2.46.0 15,271 6/25/2015
2.45.0.3 8,403 6/3/2015
2.45.0.2-beta 3,554 3/6/2015
2.45.0.1 21,704 3/3/2015
2.45.0 5,807 3/3/2015
2.44.0 57,029 10/30/2014
2.43.0 12,784 9/20/2014
2.42.0.1-beta2 3,367 8/14/2014
2.42.0.1-beta 3,446 8/13/2014
2.42.0 14,324 6/4/2014
2.41.0.1 7,618 4/7/2014
2.41.0.1-beta3 3,119 4/5/2014
2.41.0.1-beta2 3,496 4/4/2014
2.41.0 4,694 3/31/2014
2.40.0 12,707 2/25/2014
2.39.0 3,881 2/22/2014
2.35.3.3 14,524 8/29/2013
2.35.3.2 3,874 8/28/2013
2.35.3.1 3,759 8/28/2013
2.35.3 8,878 8/28/2013

v.4.14.0
   - IE Driver 4.14.0 release