.NET SDK

The .NET SDK brings the Ease surface to C#. It ships as a single NuGet package that carries the managed EaseSDK.dll alongside the native libsignal runtimes, so there is no Rust toolchain to set up and no native build step on your side.

libsignal rides inside the package and is reached over P/Invoke. You do not add it as a separate dependency, and the end-to-end encryption it backs is on for every message.

Install

The SDK is on nuget.org as EaseSDK. Releases are on the prerelease channel while the SDK is in beta, so the install asks for it explicitly:

dotnet add package EaseSDK --prerelease

The package carries the native libsignal binaries per runtime identifier, and the .NET runtime selects the right one for the deployment target: one package, one reference, nothing else to wire up.

Platform support

The package targets .NET 8+ and bundles native libsignal runtimes, reached over P/Invoke, for these runtime identifiers:

• win-x64: Windows on x64.
• win-arm64: Windows on ARM64.

The shape is the same everywhere

The .NET SDK exposes the same surface as every Ease SDK: ease.me, ease.auth, ease.contacts, and ease.chat. The calls you make and the order you make them in do not change between platforms, so the concept pages and the quickstart describe the flow you will write in C# too.

Start with authentication for how sign-up, login, and session restoration fit together, and the chat surface for how DMs and groups are addressed. The quickstart and concept samples are contract-verified in TypeScript; the same calls translate directly to C#.