From 8dce53054a70409a60770c5f1bf442daa6b79ebb Mon Sep 17 00:00:00 2001 From: Brady Gaster <41929050+bradygaster@users.noreply.github.com> Date: Fri, 12 Jun 2020 16:19:53 -0700 Subject: [PATCH] updating signalr js package readme (#22129) * updating signalr js package readme * Update src/SignalR/clients/ts/signalr/README.md Co-authored-by: Brennan * Update PatchConfig.props Co-authored-by: Brennan --- eng/PatchConfig.props | 1 + src/SignalR/clients/ts/signalr/README.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/eng/PatchConfig.props b/eng/PatchConfig.props index 0fa48bac75fb..aefa226d1519 100644 --- a/eng/PatchConfig.props +++ b/eng/PatchConfig.props @@ -63,6 +63,7 @@ Later on, this will be checked using this condition: + @aspnet/signalr; diff --git a/src/SignalR/clients/ts/signalr/README.md b/src/SignalR/clients/ts/signalr/README.md index 4a15d4eb6c6f..8015ef00dac0 100644 --- a/src/SignalR/clients/ts/signalr/README.md +++ b/src/SignalR/clients/ts/signalr/README.md @@ -1,5 +1,7 @@ JavaScript and TypeScript clients for SignalR for ASP.NET Core +> Note: The JavaScript and TypeScript clients for SignalR for ASP.NET Core have been moved to [@microsoft/signalr](https://www.npmjs.com/package/@microsoft/signalr). If you are already using `@aspnet/signalr` and are unsure when to move to `@microsoft/signalr`, check the [Feature Distribution](https://docs.microsoft.com/en-us/aspnet/core/signalr/client-features) chart in the ASP.NET Core SignalR documentation. Newer client releases are compatible with older version of ASP.NET Core SignalR which means it is safe to upgrade the client before upgrading the server. + ## Installation ```bash