We’ve just shipped the official version of the SignalR Service SDK for ASP.NET support:
Azure SignalR Service is a fully managed Azure service for real-time messaging. It is a preferred way for scaling ASP.NET Core SignalR application. However, SignalR Service is based on SignalR for ASP.NET Core 2.0, which is not 100% compatible with ASP.NET SignalR. Some code changes and proper version of dependent libraries are needed to make ASP.NET SignalR application work with SignalR Service.
We have received many usage feedbacks from customers since we announced the preview support for ASP.NET, at Microsoft Ignite 2018. Today, we are excited to announce that we have released the generally available version 1.0.0 of ASP.NET support SDK for Azure SignalR Service!
This diagram shows the typical architecture to use Azure SignalR Service with application server either written in ASP.NET Core, or now, in ASP.NET.
For self-hosted SignalR application, the application server listens to and serves client connections directly. With SignalR Service, the application server will only respond to clients’ negotiate requests, and redirect clients to SignalR Service to establish the persistent client-server connections.
Using the ASP.NET support for Azure SignalR Service you will be able to:
- Continue to keep SignalR application using ASP.NET, but work with fully managed ASP.NET Core based SignalR Service.
- Change a few lines of SignalR API codes, to switch to use SignalR Service instead of self-hosted SignalR Hubs.
- Leverage Azure SignalR Service’s built-in features and tools to help operate the SignalR application, with guaranteed SLA.
To receive the full benefit from the new ASP.NET support feature, please download and upgrade your SDKs to the latest supported versions:
Many factors, including non-technical ones, make the web application migrate from ASP.NET to ASP.NET Core difficult.
The ASP.NET support for Azure SignalR Service is to enable ASP.NET SignalR application developers to easily switch to use SignalR Service with minimal code change.
Some APIs and features are no longer supported:
- Automatic reconnects
- Forever Frame transport
- PersistentConnection class
- GlobalHost object
- HubPipeline module
- Client side Internet Explorer support before Microsoft Internet Explorer 11
ASP.NET support is focus on compatibility, so not all ASP.NET Core SignalR new features are supported. To name a few: MessagePack, Streaming, etc., are only available for ASP.NET Core SignalR applications.
SignalR Service can be configured for different service mode: Classic/Default/Serverless. For ASP.NET support, the Serverless mode is not supported.
For a complete list of feature comparison between ASP.NET SignalR and ASP.NET Core SignalR, the proper version of SDKs to use in each case, and what are the recommended alternatives to use for features discontinued in ASP.NET Core SignalR, please refer to doc here.