Packages

SignalARRR is distributed as multiple NuGet packages, one npm package, one Swift package and two Kotlin (Maven) packages. Choose the packages that match your project's role.

.NET Packages

Package	Target	Purpose
Cocoar.SignalARRR.Contracts	net8.0 / net9.0 / net10.0	[SignalARRRContract] attribute. Reference from shared interface projects.
Cocoar.SignalARRR.Server	net8.0 / net9.0 / net10.0	Server-side: HARRR hub, ServerMethods<T>, authorization, ClientManager, streaming.
Cocoar.SignalARRR.Server.Backplane.Redis	net8.0 / net9.0 / net10.0	Multi-node scale-out: AddSignalARRRRedisBackplane. Add only when running more than one node — this is where the StackExchange.Redis dependency lives.
Cocoar.SignalARRR.Server.Backplane.Postgres	net8.0 / net9.0 / net10.0	Multi-node scale-out over PostgreSQL LISTEN/NOTIFY: AddSignalARRRPostgresBackplane. For deployments whose only stateful dependency is Postgres — this is where the Npgsql dependency lives. Requires Npgsql 8.0.6 or later on every target framework, so it fits whatever version the rest of your stack (Marten, EF Core) pins.
Cocoar.SignalARRR.Client	net8.0 / net9.0 / net10.0	Client-side: HARRRConnection, typed proxies, server-to-client handlers.
Cocoar.SignalARRR.Client.FullFramework	netstandard2.0 (.NET Framework 4.6.2+)	Client for .NET Framework — typed proxies via DispatchProxy, streaming via polyfills.
Cocoar.SignalARRR.DynamicProxy	net8.0 / net9.0 / net10.0	Optional runtime proxy fallback via DispatchProxy. For plugin/dynamic scenarios.

Internal packages

These packages are referenced transitively — you normally don't need to reference them directly:

Package	Purpose
Cocoar.SignalARRR.Common	Shared types, wire protocol constants, message models
Cocoar.SignalARRR.ProxyGenerator	Base classes for proxy creation (ProxyCreator, ProxyCreatorHelper)
Cocoar.SignalARRR.SourceGenerator	Roslyn incremental source generator — a dependency of Server and Client, so it runs in the projects that use proxies

npm Package

Package	Version	Purpose
@cocoar/signalarrr	5.0.0	TypeScript/JavaScript client: HARRRConnection, invoke, send, stream, onServerMethod

Peer dependency

The npm package requires @microsoft/signalr ^10.0.0:

npm install @cocoar/signalarrr @microsoft/signalr

Swift Package

Package	Purpose
CocoarSignalARRR	Core Swift client: HARRRConnection, invoke, send, stream, onServerMethod, stream references
CocoarSignalARRRMacros	@HubProxy macro for compile-time proxy generation from Swift protocols

Dependencies

• signalr-client-swift (1.0.0-preview.1+) — Microsoft's SignalR Swift client
• swift-syntax (510.0.0+) — for macro code generation

Swift Package Manager

dependencies: [
    .package(url: "https://github.com/cocoar-dev/Cocoar.SignalARRR.git", from: "5.0.0"),
],
targets: [
    .target(
        name: "MyApp",
        dependencies: [
            .product(name: "CocoarSignalARRR", package: "Cocoar.SignalARRR"),
            .product(name: "CocoarSignalARRRMacros", package: "Cocoar.SignalARRR"),
        ]
    ),
]

Platforms: iOS 14+, macOS 11+, tvOS 14+, watchOS 7+

Kotlin Packages

Package	Purpose
dev.cocoar:signalarrr	Kotlin client for Android and the JVM: HARRRConnection, invoke, send, stream, onServerMethod, stream references, plus the plain SignalRClient underneath
dev.cocoar:signalarrr-ksp	KSP processor generating typed proxies from @HubProxy interfaces

Dependencies

• kotlinx-coroutines-core and kotlinx-serialization-json (exposed as API)
• OkHttp 5 — WebSocket, SSE and long-polling transports, file transfer
• msgpack-core — the MessagePack hub protocol, built in

Gradle

plugins {
    kotlin("plugin.serialization") version "2.4.20"
    id("com.google.devtools.ksp") version "2.3.12"
}

dependencies {
    implementation("dev.cocoar:signalarrr:5.2.0")
    ksp("dev.cocoar:signalarrr-ksp:5.2.0")
}

Platforms: Android 5+ (API 21), JVM 8+. The library is a plain Kotlin/JVM artifact with no Android SDK dependency.

Typical project setup

Shared interfaces (class library)

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Cocoar.SignalARRR.Contracts" Version="5.*" />
  </ItemGroup>
</Project>

Server (ASP.NET Core)

<ItemGroup>
  <PackageReference Include="Cocoar.SignalARRR.Server" Version="5.*" />
  <ProjectReference Include="..\Shared\Shared.csproj" />
</ItemGroup>

Optional multi-node scale-out — separate packages, so single-node applications pull in neither StackExchange.Redis nor Npgsql. Pick one:

<ItemGroup>
  <PackageReference Include="Cocoar.SignalARRR.Server.Backplane.Redis" Version="5.*" />
</ItemGroup>

builder.Services.AddSignalARRRRedisBackplane(options => options
    .WithConnectionString("localhost:6379,abortConnect=false"));

This backplane is Redis-compatible and works with Redis, Valkey, and Garnet.

<ItemGroup>
  <PackageReference Include="Cocoar.SignalARRR.Server.Backplane.Postgres" Version="5.*" />
</ItemGroup>

builder.Services.AddSignalARRRPostgresBackplane(options => options
    .WithConnectionString("Host=db;Database=app;Username=app;Password=..."));

This backplane uses the PostgreSQL primary your application already has; see Backplane & Clustering for how to choose between the two.

.NET Client (Console / WPF / etc.)

<ItemGroup>
  <PackageReference Include="Cocoar.SignalARRR.Client" Version="5.*" />
  <ProjectReference Include="..\Shared\Shared.csproj" />
</ItemGroup>

.NET Framework Client (4.6.2+ / 4.8)

For legacy .NET Framework projects (e.g., SCCM/SCSM integration, WinForms, WPF on .NET Framework):

<ItemGroup>
  <PackageReference Include="Cocoar.SignalARRR.Client.FullFramework" Version="5.*" />
</ItemGroup>

No shared interface project needed

The FullFramework client uses DispatchProxy at runtime. Define the same interface in your .NET Framework project (same namespace and method names) — no [SignalARRRContract] attribute needed.

TypeScript Client

{
  "dependencies": {
    "@cocoar/signalarrr": "^5.0.0",
    "@microsoft/signalr": "^10.0.0"
  }
}

Agent skill

Cocoar.SignalARRR.Server ships an Agent Skill — a SKILL.md plus this documentation page by page as reference files — so a coding assistant in your project knows the library's API and the mistakes it would otherwise make. It sits in a skills/ folder at the package root and takes no part in your build or your IDE: nothing is copied or shown anywhere unless you install it.

With agentskills-cli:

dotnet tool install --global agentskills-cli
agentskills-cli add Cocoar.SignalARRR.Server

That places the skill in .claude/skills/ for Claude Code and .agents/skills/ for Cursor, Codex, Copilot and other agents that read the standard; -g installs it globally instead. Without the tool, copy skills/signalarrr/ out of the package into the same folders by hand.

The skill is generated from these docs, so it says what the docs say for the version you reference. The same content is available online as llms.txt (an index with one line per page) and llms-full.txt (everything in one file) for assistants that fetch documentation by URL.

Dependency graph

The source generator comes with Server and Client as a package dependency, so a project that references both (an ASP.NET integration test project, for example) still runs it once. A contract project that references only Contracts gets no generator.

Next steps

• Getting Started — install and set up
• API Overview — public API surface
• Proxy Generation — how the source generator works