Skip to content

docs: add v9 section for strong-name signing #260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Dor-bl wants to merge 2 commits into from
+10 −5
Closed

docs: add v9 section for strong-name signing #260

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e1eff6a
docs: add v9 section for strong-name signing
Dor-bl Sep 16, 2026
d314c14
docs: fix v9 cross-reference direction in NuGet note
Dor-bl Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,14 @@ For example, some changes in the Selenium binding could break the Appium client.
> If you need deterministic builds, we recommend pinning the Selenium.WebDriver version in your own project.


## v9

Starting with `9.0.0`, the `Appium.Net` assembly shipped by the `Appium.WebDriver` package is strong-name signed with public key token `8b7475dcfe6734d4`, so it can be referenced by strongly-signed .NET assemblies. This aligns with [Selenium 4.44.0](https://github.com/SeleniumHQ/selenium/releases/tag/selenium-4.44.0), which introduced the same change to its own .NET client. See [#1066](https://github.com/appium/dotnet-client/issues/1066) and [#1118](https://github.com/appium/dotnet-client/pull/1118) for background.

> [!IMPORTANT]
> Strong naming changes the assembly identity from the previously unsigned `Appium.Net` assembly. Consumers compiled against an unsigned release, especially .NET Framework applications, should rebuild after upgrading to `9.0.0`.
> The signing key is intentionally public — it provides a stable assembly identity, not a trust or tamper-evidence guarantee.

## v8
To keep compatibility with Appium v3, most deprecated endpoint method calls have been replaced with compatible [extension command](https://appium.io/docs/en/latest/guides/execute-methods/) with [this PR](https://github.com/appium/dotnet-client/pull/939). Old drivers which still haven't implemented extension commands might not have proper implementation. Then, you will need to update Appium driver versions first.

Expand Down Expand Up @@ -113,11 +121,8 @@ Dependencies:
- [Selenium.WebDriver](http://www.nuget.org/packages/Selenium.WebDriver/)
- [System.Drawing.Common](https://www.nuget.org/packages/System.Drawing.Common/)

The `Appium.Net` assembly shipped by the `Appium.WebDriver` package is strong-name signed with public key token `8b7475dcfe6734d4`, so it can be referenced by strongly-signed .NET assemblies.

> [!IMPORTANT]
> Strong naming changes the assembly identity from the previously unsigned `Appium.Net` assembly. Consumers compiled against an unsigned release, especially .NET Framework applications, should rebuild after upgrading to the first strong-named release.

> [!NOTE]
> Starting with `9.0.0`, this assembly is strong-name signed — see [v9](#v9) above.

## Usage

Expand Down
Loading