SignalR: Reference shared framework (#28398)

* SignalR: Reference shared framework

* Update aspnetcore/signalr/hubs.md

Committing the inline suggestion, and then will update the missing link afterwards.

Co-authored-by: Rick Anderson <[email protected]>

* Moved 7.0 version up, moved new note to bottom of topics

* Removed dupe.

* added note in 5 more topics, moved latest versions to top where needed

* New include, reduced number of topics, added resources links

* Moved link in migration doc to internal.

* Added description for xref since subsection title not generated

* Removed note from hubcontext, using additional resources link now

* Reduced new section in migration topic per Rick suggestion

* Apply suggestions from code review

Added additional suggestions to link.

Co-authored-by: Rick Anderson <[email protected]>

* Moved note back to near top of hubs.md all 3 versions per Brennan suggestion

---------

Co-authored-by: Rick Anderson <[email protected]>

Author: wadepickett

aspnetcore/includes/signalr-in-shared-framework.md

@@ -0,0 +1,2 @@
+> [!NOTE]
+> ASP.NET Core SignalR server-side assemblies are now installed with the .NET Core SDK. See [SignalR assemblies in shared framework](xref:migration/22-to-30#signalr-assemblies-in-shared-framework) for more information.

aspnetcore/migration/22-to-30.md

@@ -878,6 +878,10 @@ services.AddSignalR(hubOptions =>
 
 In ASP.NET Core 2.2, you could set the `TransportMaxBufferSize` and that would effectively control the maximum message size. In ASP.NET Core 3.0, that option now only controls the maximum size before backpressure is observed.
 
+#### SignalR assemblies in shared framework
+
+ASP.NET Core SignalR server-side assemblies are now installed with the .NET Core SDK. For more information, see [Remove obsolete package references](#remove-obsolete-package-references) in this document.
+
 ### MVC controllers
 
 Mapping of controllers now takes place inside `UseEndpoints`.

aspnetcore/signalr/api-design.md

@@ -75,3 +75,7 @@ The older clients won't be expecting the `Sender` value, so they'll ignore it. A
 [!code-typescript[OnWithObjectNew](api-design/sample/Samples.ts?name=OnWithObjectNew&highlight=2-5)]
 
 In this case, the new client is also tolerant of an old server that doesn't provide the `Sender` value. Since the old server won't provide the `Sender` value, the client checks to see if it exists before accessing it.
+
+## Additional resources
+
+* [SignalR assemblies in shared framework](xref:migration/22-to-30#signalr-assemblies-in-shared-framework)

aspnetcore/signalr/hubcontext.md

@@ -5,7 +5,7 @@ description: Learn how to use the ASP.NET Core SignalR HubContext service for se
 monikerRange: '>= aspnetcore-2.1'
 ms.author: bradyg
 ms.custom: mvc
-ms.date: 02/13/2023
+ms.date: 02/20/2023
 uid: signalr/hubcontext
 ---
 # Send messages from outside a hub
@@ -149,6 +149,7 @@ This is useful when:
 
 ## Additional resources
 
+* [SignalR assemblies in shared framework](xref:migration/22-to-30#signalr-assemblies-in-shared-framework)
 * <xref:tutorials/signalr>
 * <xref:signalr/hubs>
 * <xref:signalr/publish-to-azure-web-app>