We’ve just released the second preview of the upcoming 2.4.0 release of ASP.NET SignalR. As we mentioned in our previous blog post on the future of ASP.NET SignalR we are releasing a minor update to ASP.NET SignalR (the version of SignalR for System.Web and/or OWIN-based applications) that includes, support for the Azure SignalR Service, as well as some bug fixes and minor features.

We recommend you try upgrading to the preview even if you’re not interested in adopting the Azure SignalR Service at this time. Your feedback is critical to making sure we produce a stable and compatible update! You can find details about the release on the releases page of the ASP.NET SignalR GitHub repository.

Highlights

This preview mostly contains further bug fixes and changes to support the Azure SignalR service. Some of the major fixes include:

• Fixed issues when using .off and .on with “bound” functions in the JavaScript Client
• Removed a deadlock in the .NET client
• Added detection and a clear error message when connecting to an ASP.NET Core SignalR Service, since those are incompatible
• Suppressed a spurious ObjectDisposedExceptions thrown by a background task
• Set an appropriate Content-Type header value to prevent warnings in browser consoles (a community contribution!)
• Fixed a socket leak that can occur when HTTP requests fail
• Add support for WebSockets to the .NET Standard 2.0 client
• Enabled full support for SourceLink to allow stepping in to SignalR source code when debugging
• Fixed asssembly load errors when using ‘signalr.exe’ with an app that has upgraded Newtonsoft.Json
• Fixed a memory leak that can occur if OnDisconnected throws

Other minor fixes are included, for a full list see our GitHub issue tracker