Skip to content

Light Freshness: ASP.NET - SignalR (7 topics) #37165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wadepickett merged 9 commits into from
May 22, 2026
Merged

Light Freshness: ASP.NET - SignalR (7 topics) #37165

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
fd7faf3
refresh content
GitHubber17 May 18, 2026
3b4a569
refresh content
GitHubber17 May 19, 2026
f52f756
refresh content
GitHubber17 May 20, 2026
cf4dc5b
refresh content
GitHubber17 May 20, 2026
ef38fc1
Merge branch 'main' into 568764-o
GitHubber17 May 20, 2026
22040d6
refresh content
GitHubber17 May 21, 2026
300d2e4
edits
GitHubber17 May 21, 2026
6532fbc
refresh content
GitHubber17 May 21, 2026
3c00531
Apply suggestions from code review
GitHubber17 May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aspnetcore/blazor/fundamentals/signalr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ hubConnection = new HubConnectionBuilder()

The preceding example configures the hub connection URL to the absolute URI address at `/chathub`. The URI can also be set via a string, for example `https://signalr.example.com`, or via [configuration](xref:blazor/fundamentals/configuration). `Navigation` is an injected <xref:Microsoft.AspNetCore.Components.NavigationManager>.

For more information, see <xref:signalr/configuration#configure-additional-options>.
For more information, see <xref:signalr/configuration#configure-other-options>.

## Client-side rendering

Expand Down
2 changes: 1 addition & 1 deletion aspnetcore/includes/signalr-in-shared-framework.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +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.
> ASP.NET Core SignalR server-side assemblies are now installed with the .NET Core SDK. For more information, see [SignalR assemblies in shared framework](xref:migration/22-to-30#signalr-assemblies-in-shared-framework).
2 changes: 1 addition & 1 deletion aspnetcore/release-notes/aspnetcore-9/includes/signalr-trimming-aot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,6 @@ The preceding example produces a native Windows executable of 10 MB and a Linux
* As shown in the preceding code, apps that use JSON serialization and Native AOT must use the `System.Text.Json` Source Generator.
* This follows the same approach as Minimal APIs.
* On the SignalR server, Hub method parameters of type `IAsyncEnumerable<T>` and `ChannelReader<T>` where `T` is a ValueType (`struct`) aren't supported. Using these types results in a runtime exception at startup in development and in the published app. For more information, see [SignalR: Using IAsyncEnumerable&lt;T&gt; and ChannelReader&lt;T&gt; with ValueTypes in native AOT (`dotnet/aspnetcore` #56179)](https://github.com/dotnet/aspnetcore/issues/56179).
* [Strongly typed hubs](xref:signalr/hubs#strongly-typed-hubs) aren't supported with Native AOT (`PublishAot`). Using strongly typed hubs with Native AOT will result in warnings during build and publish, and a runtime exception. Using strongly typed hubs with trimming (`PublishedTrimmed`) is supported.
* [Strongly typed hubs](xref:signalr/hubs#use-strongly-typed-hubs) aren't supported with Native AOT (`PublishAot`). Using strongly typed hubs with Native AOT will result in warnings during build and publish, and a runtime exception. Using strongly typed hubs with trimming (`PublishedTrimmed`) is supported.
* Only `Task`, `Task<T>`, `ValueTask`, or `ValueTask<T>` are supported for async return types.

69 changes: 37 additions & 32 deletions aspnetcore/signalr/authn-and-authz.md
View file
Open in desktop

Large diffs are not rendered by default.

8 changes: 4 additions & 4 deletions aspnetcore/signalr/background-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Hosting ASP.NET Core SignalR Hubs in the context of a background worker process

In the preceding example, the `ClockHub` class implements the `Hub<T>` class to create a strongly typed Hub. The `ClockHub` has been configured in `Program.cs` to respond to requests at the endpoint `/hubs/clock`.

For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#strongly-typed-hubs).
For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#use-strongly-typed-hubs).

> [!NOTE]
> This functionality isn't limited to the [Hub\<T>](xref:Microsoft.AspNetCore.SignalR.Hub`1) class. Any class that inherits from [Hub](xref:Microsoft.AspNetCore.SignalR.Hub), such as [DynamicHub](xref:Microsoft.AspNetCore.SignalR.DynamicHub), works.
Expand Down Expand Up @@ -93,7 +93,7 @@ Hosting ASP.NET Core SignalR Hubs in the context of a background worker process

In the preceding example, the `ClockHub` class implements the `Hub<T>` class to create a strongly typed Hub. The `ClockHub` has been configured in the `Startup` class to respond to requests at the endpoint `/hubs/clock`.

For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#strongly-typed-hubs).
For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#use-strongly-typed-hubs).

> [!NOTE]
> This functionality isn't limited to the [Hub\<T>](xref:Microsoft.AspNetCore.SignalR.Hub`1) class. Any class that inherits from [Hub](xref:Microsoft.AspNetCore.SignalR.Hub), such as [DynamicHub](xref:Microsoft.AspNetCore.SignalR.DynamicHub), works.
Expand Down Expand Up @@ -156,7 +156,7 @@ Hosting ASP.NET Core SignalR Hubs in the context of a background worker process

In the preceding example, the `ClockHub` class implements the `Hub<T>` class to create a strongly typed Hub. The `ClockHub` has been configured in the `Startup` class to respond to requests at the endpoint `/hubs/clock`.

For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#strongly-typed-hubs).
For more information on strongly typed Hubs, see [Use hubs in SignalR for ASP.NET Core](xref:signalr/hubs#use-strongly-typed-hubs).

> [!NOTE]
> This functionality isn't limited to the [Hub\<T>](xref:Microsoft.AspNetCore.SignalR.Hub`1) class. Any class that inherits from [Hub](xref:Microsoft.AspNetCore.SignalR.Hub), such as [DynamicHub](xref:Microsoft.AspNetCore.SignalR.DynamicHub), works.
Expand Down Expand Up @@ -212,4 +212,4 @@ During the `IHostedService.StopAsync` method, the `HubConnection` is disposed of
* [Get started](xref:tutorials/signalr)
* [Hubs](xref:signalr/hubs)
* [Publish to Azure](xref:signalr/publish-to-azure-web-app)
* [Strongly typed Hubs](xref:signalr/hubs#strongly-typed-hubs)
* [Strongly typed Hubs](xref:signalr/hubs#use-strongly-typed-hubs)
Loading
Loading