You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SignalR clients ship alongside the server components and are versioned to match. Any supported client can safely connect to any supported server, and any compatibility issues would be considered bugs to be fixed. SignalR clients are supported in the same support lifecycle as the rest of .NET Core. See [the .NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) for details.
16
+
17
+
Many features require a compatible client **and** server. See below for a table showing the minimum versions for various features.
18
+
19
+
The 1.x versions of SignalR map to the 2.1 and 2.2 .NET Core releases and have the same lifetime. For version 3.x and above, the SignalR version exactly matches the rest of .NET and has the same support lifecycle.
20
+
21
+
| SignalR version | .NET Core version | Support level | End of support |
22
+
| - | - | - | - |
23
+
| 1.0.x | 2.1.x | Long Term Support | August 21, 2021 |
24
+
| 1.1.x | 2.2.x | End Of Life | December 23, 2019 |
25
+
| 3.x or higher |*same as SignalR version*| See the [the .NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core)|
26
+
27
+
**NOTE:** In ASP.NET Core 3.0, the JavaScript client *moved* to the `@microsoft/signalr` npm package.
12
28
13
29
## Feature distribution
14
30
15
31
The table below shows the features and support for the clients that offer real-time support. For each feature, the *minimum* version supporting this feature is listed. If no version is listed, the feature isn't supported.
16
32
17
-
| Feature | .NET | JavaScript | Java |
18
-
| ---- | :-: | :-: | :-: |
19
-
| Azure SignalR Service Support |1.0.0|1.0.0|1.0.0|
0 commit comments