Release v1.11.0

Features

Management SDK

1. ServiceHubContext now implements IDisposable.
2. All methods in ServiceHubContext.ClientManager are supported with persistent transport type.
3. Remove limitation on setting ServiceManagerOptions.ServiceEndpoints with transient transport type. Now no matter what transport type is, you can use DefaultAzureCredential as follows:

    var serviceManager = new ServiceManagerBuilder().WithOptions(option =>
    {
        option.ServiceEndpoints = new ServiceEndpoint[] { new ServiceEndpoint(new Uri("https://<your-signalr-name>.service.signalr.net"), new DefaultAzureCredential()) };
    })
    .BuildServiceManager();

Protocol

1. Add more property to GroupBroadcastMessage (#1429)

Bug fixes

1. Fix a bug in ServiceManager.IsServiceHealthy that throws exception. (#1430)

Release v1.10.0

Features

1. Management SDK publishes a new set of APIs to replace the old APIs mainly to support multiple Azure SignalR instances, but the new set of APIs also provide additional benefits.
   • Check Migration guide from version 1.9.x and below to 1.10.0 for migration benefits and steps.
   • For users who haven't used Management SDK before, you can read this doc directly for an introduction about Management SDK.
   • ServiceManagerBuilder.Build(), IServiceManagerBuilder are obsolete.
2. SDK client will also send AccessKey request via server connection when using aad auth. [ #1361 ]
3. Add ServiceEndpoint constructor for aad scenario.

   var endpoint = new ServiceEndpoint(new Uri("https://canary-aad-test.service.signalr.net"), new DefaultAzureIdentity());

4. ServiceEndpoint.Endpoint will convert its hostname into lowercase even when the given hostname is in uppercase. It will also influence the generated accessToken and URL. RFC4343
5. ServiceEndpoint.Endpoint will automatically add a port postfix if port=xxx was in the connection string and was not equal to 80 when HTTP or 443 when HTTPS.
6. According to 5, endpoints with the same hostname but have different ports will NOT be considered equal.

Bug fixes

1. Fix a bug that will let migrated connections dropped unexpectedly when the app task on the old server could not stop immediately. [ #1376 ]

Known issues:

1. In Management SDK / Serverless SDK, ServiceHubContext.ClientManager is not ready with Persistent transport type.

Release v1.9.2

Features

1. Add a WithNewtonsoftJson method for ServiceManagerBuilder (#1351)

Bug fixes

1. Fix #1346 that DetectedLongRunningApplicationTask warning on each websocket connection (#1350)

Release v1.9.1

Improvements

1. For ASP.NET Core SignalR, the SDK no longer cancels long-running client hub logic when the client disconnects, this behavior change makes the behavior consistent with the self-host SignalR, the discussion leading to this change is #1318 (#1332)

Bug fixes

1. Workaround fix for connection migration (#1342)

Release v1.9.0

1. Remove Microsoft.Azure.Services.AppAuthentication dependency.
2. Add Azure.Identity dependency to support modern AAD features.

Release v1.8.2

Improvements:

1. add new service events: BufferFull (#1274)
2. Implement SendAllExcept and SendToGroupExcept for transient mode (#1287)
3. Improve connection drop logs (#1277)
4. add connection stat hook. (#1280)

Release V1.8.1

1. Add support for user-assigned manage identity
   1. To use user-assigned managed identity, you can add a ClientId=xxxxx in your aad connection string.

      Endpoint=<endpoint>;AuthType=aad;ClientId=<User-Assigned Managed Identity clientId>

Releasing v1.8.0

Features:

1. Add ServiceEventMessage in service protocol. (#1208)
   1. One typical usage would be to monitor and log service events.

Bug fixes:

1. Fix #1236 Fix reconnect traffic spike when switching from self-hosted AspNet SignalR to azure (#1228)

Releasing v1.7.1

1. Fix #1200 Expected a handshake response from the server
2. Fix #1206 Microsoft.Azure.SignalR.Management 1.7.0 constantly tries to establish socket connection to SignalR service

Releasing v1.7.0

Features:

1. Support .NET 5.0 (#1101)