A library for ASP.NET Core developers to add real-time web functionality with server-to-client content push.
ASP.NET Core SignalR is a library that simplifies adding real-time web functionality to ASP.NET Core applications. It enables server-side code to push content to connected clients instantly, supporting features like live chats, notifications, and real-time dashboards. The library abstracts complex transport protocols, making it accessible for developers.
ASP.NET Core developers building applications that require real-time client-server communication, such as collaborative tools, gaming platforms, or live data monitoring systems.
Developers choose SignalR for its seamless integration with ASP.NET Core, built-in support for WebSockets with automatic fallbacks, and ease of use in implementing real-time features without managing low-level protocol details.
[Archived] Incredibly simple real-time web for ASP.NET Core. Project moved to https://github.com/aspnet/AspNetCore
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built directly into the ASP.NET Core framework, making it effortless to add real-time capabilities to existing .NET web applications without low-level protocol management.
Automatically uses WebSockets as the primary transport with fallbacks to Server-Sent Events or long polling for compatibility, as highlighted in the features, ensuring reliable connections.
Supports the optional MessagePack protocol via a separate npm package (@aspnet/signalr-protocol-msgpack), reducing message size and improving performance for high-frequency updates.
Provides official JavaScript/TypeScript clients for browsers and Node.js, with clear npm installation instructions, facilitating easy integration across frontend platforms.
The GitHub repo is archived, with development moved to the main ASP.NET Core repo, which can cause confusion and fragmented community support for issues and updates.
Tightly coupled with ASP.NET Core, requiring a .NET backend and limiting flexibility for mixed or non-.NET technology stacks, as noted in the README's focus.
Setting up advanced features like MessagePack involves additional npm packages and strict version alignment between client and server, increasing setup complexity compared to simpler alternatives.