Skip to content

Releases: Azure/azure-signalr

V1.2.1 SDK for SignalR

15 Nov 05:09
8c93b95
Compare
Choose a tag to compare

Management API

  1. Fix #733 that new version(4.6.0) of System.IO.Pipelines changed the default value of PipeOptions' .ctor, and causing PipeWriter.GetMemory to return null when in runtime time the version is rebinded to old version of System.IO.Pipelines, which is the case for Azure Function cli as it sticky to version 4.5.3.

V1.2.0 SDK for SignalR

07 Nov 07:00
782eaf1
Compare
Choose a tag to compare

General

  1. Upgrade System.IO.Pipelines depedency version to 4.6.0 (#671)
  2. Integrate with SignalR's option EnableDetailedErrors, only when it is enabled that clients can view detailed errors (#694)
  3. Improve ServiceConnectionBase logic to reduce task waiting (#672)

ASP.NET Core SignalR

  1. Fixes #693 when standard SignalR is used together with blazor (#695)

ASP.NET SignalR SDK

  1. Add EventSource provider to default logger factory for better debugging experience (#684)
  2. Fix #700 when the SDK is used together with 3.0 Microsoft.AspNetCore.Http.Connections.Client (#701)

Management API

  1. Fix #677 that connection reconnects right after StopAsync is called (#707)

V1.1.1 SDK for SignalR

30 Sep 05:43
e731ef9
Compare
Choose a tag to compare

General

  1. Fix #673 to use released package version(#670)

V1.1.0 SDK for SignalR

24 Sep 03:01
f450048
Compare
Choose a tag to compare

General

Support .NET Core 3.0.

V1.0.14 SDK for SignalR

11 Sep 06:26
368b665
Compare
Choose a tag to compare

General

  1. Fix #647 to avoid potential memory leak in Microsoft.IdentityModel.Tokens.JWT version 5.5.0. (#653)

V1.0.1 Management SDK for ASP.NET Core SignalR

03 Sep 05:42
50c0877
Compare
Choose a tag to compare

V1.0.13 SDK for SignalR

02 Sep 08:34
c764ee7
Compare
Choose a tag to compare

General

  1. Fix #632 to throw TimeOutException when JoinGroup/LeaveGroup actions timeout (#638)

V1.0.12 SDK for SignalR

14 Aug 03:20
b58ad94
Compare
Choose a tag to compare

General

  1. Fix #416, #539 that in some corner cases, OnDisconnected event is not invoked. #612

ASP.NET Core

  1. Fix #623: Improve the robustness of the logic getting Context.GetHttpContext().Connection.RemoteIpAddress. #626

V1.0.0 Management SDK for ASP.NET Core SignalR

25 Jul 02:48
a2c91ca
Compare
Choose a tag to compare

SDK for Microsoft.Azure.SignalR.Management

Install-Package Microsoft.Azure.SignalR.Management -Version 1.0.0

Features:

  1. Support adding connection to a group.
serviceHubContext.Groups.AddToGroupAsync(connectionId, groupName);
  1. Support removing connection from a group.
serviceHubContext.Groups.RemoveFromGroupAsync(connectionId, groupName);
  1. Support send messages to a connection.
serviceHubContext.Clients.Client(connectionId).SendAsync(MethodName, Message)

V1.0.11 SDK for SignalR

19 Jul 08:37
e6081a6
Compare
Choose a tag to compare

General

  1. Group add and remove now wait for ack message from service, so that group related messages are now no need to be sticky to a particular server connection. #417 Do use await to guarantee the delivery, for example:
await Groups.AddToGroupAsync(..);
  1. Fix multi-endpoint bug that the endpoint status should be isolated for different hubs. #555
  2. Improve multi-endpoint status change logic, change to push mode instead of pulling the status for every request. #570
  3. For secondary endpoints, the endpoint is set as inactive if there is no client connected to that endpoint. Messages will not be sent to inactive secondary endpoints. #576
  4. access_token is no longer the one that our service relies on to do session sticky. A query parameter asrs_request_id is leveraged to do session sticky. For ASP.NET SignalR, a new version 2.4.1 of client is required to enable this. #587

ASP.NET Core SignalR

  1. Fix cases that customer's application layer logic might prevent server connection from recovering #590

ASP.NET SignalR

  1. Partially fix #473 , now QueryString and Headers can be fetched from Context.Request. #601
  2. Fix cases that customer's application layer logic might lead to connections not cleaned up clearly #595