dotnet-managedcode-orleans-signalr

Coordinates SignalR real-time message delivery from Orleans grains in distributed .NET applications.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-managedcode-orleans-signalr-zhenpenglai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-managedcode-orleans-signalr
Source: https://github.com/zhenpengLai/myuseskill/tree/main/dotnet-managedcode-orleans-signalr
Command: npx skills add https://github.com/zhenpengLai/myuseskill --skill dotnet-managedcode-orleans-signalr-zhenpenglai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Distributed .NET applications that combine Orleans and SignalR often blur the boundary between grain domain logic and real-time transport, leading to tangled code and unverified message delivery. This Skill guides the integration of ManagedCode.Orleans.SignalR so grain events reliably reach connected clients. ## Core Features & Use Cases - Integration Guidance: Determines where the Orleans-to-SignalR bridge belongs and keeps grain logic separate from transport concerns. - Targeting Documentation: Documents how user, group, or connection targeting is resolved for hub delivery. - End-to-End Validation: Verifies real-time delivery from grain event to connected client, not just registration code. - Use Case: A chat backend where Orleans grains track room state and must push updates to SignalR groups; this Skill structures the grain-to-hub push flow and validates delivery. ## Quick Start Use this Skill to review how my Orleans grains publish events to SignalR clients and validate the end-to-end delivery flow.

Frequently Asked Questions about dotnet-managedcode-orleans-signalr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send SignalR messages from Orleans grains?▼

Use ManagedCode.Orleans.SignalR to bridge grain events to SignalR hub delivery. Keep domain logic inside grains and let the integration layer handle transport, then validate delivery from grain event to connected client end to end.

How to target SignalR users, groups, or connections from Orleans?▼

Resolve targeting at the integration boundary rather than inside grain logic. Document how user, group, or connection identifiers map from Orleans state to SignalR addressing so push flows remain traceable.

When should I combine Orleans and SignalR in one application?▼

Combine them only when distributed grain state or orchestration must drive real-time client updates, such as chat rooms or live dashboards. Confirm the need first; mixing the two casually adds complexity without benefit.

Why is my Orleans grain event not reaching SignalR clients?▼

Delivery failures often come from validating only registration code instead of the full path. Trace the flow from grain event through the ManagedCode.Orleans.SignalR integration to hub delivery and the connected client or group.

What are the limitations of grain-driven SignalR push flows?▼

Grain-driven pushes require clear separation between domain logic and transport concerns, and targeting resolution must be explicit. Without end-to-end validation, silent delivery gaps can occur between grain events and clients.