Releases: Azure/azure-signalr
Releases · Azure/azure-signalr
v1.0.5 for ASP.NET Core SignalR
v1.0.0-preview1-10275 for ASP.NET SignalR
v1.0.0-preview1-10264 for ASP.NET SignalR
v1.0.4 for ASP.NET Core SignalR
Improvements
- 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
v1.0.0-preview1-10259 for ASP.NET SignalR
Improvements
MapAzureSignalR
is also able to customServiceOptions
throughAction<ServiceOptions>
now. #240- Trace is now enabled, set the trace level to
Information
for more logs from server side, tryGlobalHost.TraceManager.Switch.Level = SourceLevels.Information;
#247 - Server connections will always try reconnecting to Azure Service, with frequency up to one minute at most. #233
- A new
ServerCloseMessage
message type is introduced. Now server side can report much more detailed error message from service side. #236
Fixes
- Fix a false warning when dispatching message #248
v1.0.2 for ASP.NET Core SignalR
Fixes
- Fix the issue that user claims are not included in jwt token (#235)
v1.0.1 for ASP.NET Core SignalR
Fixes
- Custom
NameClaimType
andRoleClaimType
will be preserved. (#223 )
v1.0.0-preview1-10247 for ASP.NET SignalR
Fixes
- Custom
NameClaimType
andRoleClaimType
will be preserved. (#223 )
v1.0.0-preview1-10233 for ASP.NET SignalR
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 |