v1.1.0-preview1-10442 for ASP.NET Core SignalR

Support .NET Core 3.0 Preview7

v1.1.0-preview1-10384 for ASP.NET Core SignalR

Feature:

Support .NET Core 3.0 Preview6

V1.0.10 SDK for SignalR

1. SDK for ASP.NET Core SignalR

Install-Package Microsoft.Azure.SignalR -Version 1.0.10

Features:

1. Add option for ServerStickyMode in case customer has need to make sure negotiation server and hub server are the same one.
2. Change default server connection count per hub to 2 as we support auto re-balance server connections now.

2. SDK for ASP.NET SignalR

Install-Package Microsoft.Azure.SignalR.AspNet -Version 1.0.10

Features:

1. Add option for ServerStickyMode in case customer has need to make sure negotiation server and hub server are the same one.
2. Enable isolation per application name. Fix #348
3. Change default server connection count per hub to 2 as we support auto re-balance server connections now.

V1.0.0-preview1-10420 Management SDK for ASP.NET Core SignalR

SDK for Microsoft.Azure.SignalR.Management

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

Features:

1. Support removing a specific user from all groups.

Bug fixes:

1. Send correct user-agent header to Azure SignalR Service.

v1.0.9 for ASP.NET Core SignalR

Features:

1. Add an ApplicationName option to ServiceOptions so that user now can share one Azure endpoint for different environments, as described in #348. Thanks @steverash for providing this cool feature #449

Bug fixes:

1. Fix the issue that user's aud claim is ignored when reconstructing the HttpContext for Hub. #465
2. Fix #480 that connection strings customized is not overwriting the ones from configurations. #481

v1.0.0 for ASP.NET SignalR

We are releasing the generally available version 1.0.0 for ASP.NET SignalR support.

Features:

1. Simplify the trace source name to Microsoft.Azure.SignalR for Azure SignalR. #471
2. For #373, downgrade some transient server connection errors to warnings to reduce noises. #482

Bug fixes:

1. Fix the issue that user's aud claim is ignored when reconstructing the HttpContext for Hub. #465
2. Fix #480 that connection strings customized is not overwriting the ones from configurations. #481
3. Fix #452 that when using net462 or below, server connection fails with assembly not found error for System.Runtime.InteropServices.RuntimeInformation. #499

v1.1.0-preview1-10384 for ASP.NET Core SignalR

Feature:

Add ASP.NET Core 3.0 Preview support with Azure SignalR Service.

From ASP.NET Core 3.0, switching between local SignalR and Azure SignalR Service could be easier by simply assign HostingStartupAssembly in the launch settings or a call to AddAzureSignalR(). Check Server-side Blazor Sample for details.

v1.0.8 for ASP.NET Core SignalR

Bug fixes:

1. Fix dead client connections didn't remove from manager. (#402)
2. Fix router bug when SendToConnection for multi-endpoints
3. Fix the duplicate endpoint false alert as described in #439

Feature:

1. Releasing Management SDK for Azure SignalR Service. You can use this SDK to manage your SignalR clients connected to your Azure SignalR Service directly such as broadcast messages. You can refer to Management Samples for more information about this SDK.

Breaking changes:

1. Interface update for sharding usage, adding HttpContext as input parameters when negotiate

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

Bug fixes:

1. Fix router bug when SendToConnection for multi-endpoints
2. Move authorization check in negotiate stage for ASP.NET (#419)

Breaking changes:

1. Interface update for sharding usage, adding IOwinContext as input parameters when negotiate

v1.0.7 for ASP.NET Core SignalR

Improvements:

1. Simplify IEndpointRouter
2. Provide an EndpointRouterDecorator to use.
3. Enable server connections re-balance with on-demand connections #355