Skip to content

Releases: Azure/azure-signalr

v1.0.5 for ASP.NET Core SignalR

24 Dec 07:27
c77470e
Compare
Choose a tag to compare

Improvements

  1. Server side heartbeat mechanism is changed to ping-pong mode to improve server stability (#246, #280, #222)

Bug Fixes

  1. Fix IndexOutOfRangeException when service connections are not ready (#294)

v1.0.0-preview1-10275 for ASP.NET SignalR

24 Dec 07:26
6730bbf
Compare
Choose a tag to compare

Improvements

  1. Server side heartbeat mechanism is changed to ping-pong mode to improve server stability (#246, #280, #222)
  2. Use Channel to asynchronously dispatch messages so that the whole workflow is not blocked by long run OnConnected or OnReconnected user code. (#268)

v1.0.0-preview1-10264 for ASP.NET SignalR

30 Nov 03:23
1d124e3
Compare
Choose a tag to compare

Improvements

  1. Expose connection string to MapAzureSignalR #272
  2. ASP.NET ServiceOptions can customize claims now #265
  3. Add a random asrs.id request id in JWT token to improve traffic load balancing, because Azure SignalR uses jwt token to do sticky session now.

v1.0.4 for ASP.NET Core SignalR

30 Nov 03:24
c7d58ee
Compare
Choose a tag to compare

Improvements

  1. Add a random asrs.id request id in JWT token to improve traffic load balancing, because Azure SignalR uses jwt token to do sticky session now.

v1.0.3 for ASP.NET Core SignalR

15 Nov 05:50
9a61ec3
Compare
Choose a tag to compare

Improvements

  1. Server connections will always try reconnecting to Azure Service, with frequency up to one minute at most. #233
  2. A new ServerCloseMessage message type is introduced. Now server side can report much more detailed error message from service side. #236

v1.0.0-preview1-10259 for ASP.NET SignalR

15 Nov 05:47
e58c4e6
Compare
Choose a tag to compare

Improvements

  1. MapAzureSignalR is also able to custom ServiceOptions through Action<ServiceOptions> now. #240
  2. Trace is now enabled, set the trace level to Information for more logs from server side, try GlobalHost.TraceManager.Switch.Level = SourceLevels.Information; #247
  3. Server connections will always try reconnecting to Azure Service, with frequency up to one minute at most. #233
  4. A new ServerCloseMessage message type is introduced. Now server side can report much more detailed error message from service side. #236

Fixes

  1. Fix a false warning when dispatching message #248

v1.0.2 for ASP.NET Core SignalR

19 Oct 06:13
1db56c6
Compare
Choose a tag to compare

Fixes

  • Fix the issue that user claims are not included in jwt token (#235)

v1.0.1 for ASP.NET Core SignalR

17 Oct 02:59
941dc33
Compare
Choose a tag to compare

Fixes

  • Custom NameClaimType and RoleClaimType will be preserved. (#223 )

v1.0.0-preview1-10247 for ASP.NET SignalR

17 Oct 03:01
a1462fa
Compare
Choose a tag to compare

Fixes

  • Custom NameClaimType and RoleClaimType will be preserved. (#223 )

v1.0.0-preview1-10233 for ASP.NET SignalR

22 Sep 01:56
1ca3ead
Compare
Choose a tag to compare

This is the first preview for supporting ASP.NET SignalR on Azure SignalR Service.

This version of Azure ASP.NET SignalR SDK supports Hubs. Persistent Connections are not yet supported.

Enabling Azure SignalR for your ASP.NET SignalR is very simple, ChatSample shows detailed steps on how to.

The following package has been released to NuGet.org:

Package ID Version
Microsoft.Azure.SignalR.AspNet 1.0.0-preview1-10233