You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
linkTitle: ".NET Assemblies Are Now Strongly Signed"
4
+
date: 2026-04-27
5
+
tags: ["selenium", "dotnet"]
6
+
categories: ["general"]
7
+
author: Nikolay Borisenko [@nvborisenko](https://github.com/nvborisenko)
8
+
description: >
9
+
Starting with Selenium 4.44, the main NuGet packages ship strongly signed assemblies. The separate StrongNamed packages are retired.
10
+
---
11
+
12
+
Starting with **Selenium 4.44**, the `Selenium.WebDriver` and `Selenium.Support` NuGet packages ship **strongly signed assemblies**. The separate `Selenium.WebDriver.StrongNamed` and `Selenium.Support.StrongNamed` packages are discontinued.
13
+
14
+
## Why This Matters
15
+
16
+
Without strong naming on the official packages, any project that itself needed to be strongly signed could not reference Selenium from NuGet. Teams were forced to either forgo strong naming, bundle out-of-band downloads, or use the separate `StrongNamed` packages with a different assembly name — all of which caused friction, especially in enterprise environments.
17
+
18
+
## What Changed
19
+
20
+
-`Selenium.WebDriver` and `Selenium.Support` are now strongly signed.
If you use the regular packages — the assemblies are now signed but the assembly names change (`WebDriver.dll` → `Selenium.WebDriver.dll`, `WebDriver.Support.dll` → `Selenium.Support.dll`), so update any explicit assembly references accordingly. The public API is unchanged.
34
+
35
+
## Related Issues
36
+
37
+
-[#12315](https://github.com/SeleniumHQ/selenium/issues/12315) — Publish StrongNamed builds to NuGet feed
38
+
-[#10845](https://github.com/SeleniumHQ/selenium/issues/10845) — Revisiting strong-named assemblies for NuGet
39
+
-[#14115](https://github.com/SeleniumHQ/selenium/issues/14115) — Strong Name Key
0 commit comments