Verify SignalR Overview up to date - referesh.

[wadepickett]

Description

This is a high traffic article that has not been updated for a while. Verify it is up to date and refresh if needed.

Verify it is up to date for ASP.NET Core in .NET 10

Check for clarity and acuracy and follow repo guidelines.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-10.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/signalr/introduction.md

Document ID

1986d76e-63e7-8a2d-c8a4-9c132d2b0ee1

Platform Id

9c8c9921-e22b-09d2-2ec7-e80759dfd726

Article author

@wadepickett

Metadata

• ID: a26c63dd-9fdc-7d8d-aec4-4343807ee312
• PlatformId: 9c8c9921-e22b-09d2-2ec7-e80759dfd726
• Service: aspnet-core
• Sub-service: aspnetcore-signalr

Related Issues

[wadepickett]

🤖 AI Triage Summary

📌 Note to community: This is an automated preliminary analysis to help our documentation team quickly review, determine scope and prioritize this issue. This report is not a resolution — the documentation team will make all final decisions.

---

This preliminary assessment report was run by: @wadepickett
Date: 2026-04-19
Issue: 37025
Model: GitHub Copilot

---

Issue Analysis: Verify and Refresh SignalR Overview Article for .NET 10

✅ Issue Validation

Status: Valid and actionable

📋 Issue Summary

The SignalR overview article (introduction.md) is a high-traffic page that has not been substantially updated. The ms.date is 12/02/2024. Several sections contain outdated information, are missing features introduced in .NET 9, and include legacy guidance (ES6/ES5 transpiling) that is no longer relevant for modern audiences. The article also lacks depth expected of a high-traffic overview.

📁 Potentially Affected Files

These files have been identified as possibly related to this issue and may need review.

File	Path	Lines	Section
Main article	aspnetcore/signalr/introduction.md	1-65	Entire article
ES6 include	aspnetcore/includes/SignalR/es6.md	1-5	ES6 transpiling guidance

📝 Preliminary Change Assessment

The following are initial observations for the documentation team to evaluate—not final decisions.

1. Outdated ES6/ES5 Transpiling Section

File: aspnetcore/signalr/introduction.md
Location: Line 54 (include reference) → aspnetcore/includes/SignalR/es6.md
Type: Remove or significantly update

Current content:

[!INCLUDE[](~/includes/SignalR/es6.md)]

Which renders:

SignalR targets ES6. For browsers that don't support ES6, transpile the library to ES5. For more information, see Getting Started with ES6 – Transpiling ES6 to ES5 with Traceur and Babel.

Issue: ES6 is universally supported by all modern browsers. Referencing Traceur for transpiling is very dated (Traceur is essentially unmaintained). This section and its include are no longer useful for a .NET 10 audience. Consider removing the include reference and the "Browsers that don't support ECMAScript 6 (ES6)" link from Additional resources (line 63).

2. Missing .NET 9 Features in Feature List

File: aspnetcore/signalr/introduction.md
Location: Lines 26-33 (feature list)
Type: Add new items

Current content (lines 26-33):

Here are some features of SignalR for ASP.NET Core:

* Handles connection management automatically.
* Sends messages to all connected clients simultaneously. For example, a chat room.
* Sends messages to specific clients or groups of clients.
* Scales to handle increasing traffic.
* [SignalR Hub Protocol](https://github.com/dotnet/aspnetcore/blob/main/src/SignalR/docs/specs/HubProtocol.md)

Suggested direction — consider adding:

Here are some features of SignalR for ASP.NET Core:

* Handles connection management automatically.
* Sends messages to all connected clients simultaneously. For example, a chat room.
* Sends messages to specific clients or groups of clients.
* Scales to handle increasing traffic.
* Supports trimming and Native AOT (ahead-of-time) compilation (.NET 9+).
* Provides built-in support for OpenTelemetry-based distributed tracing and diagnostics (.NET 9+).
* Supports polymorphic type handling in hub methods (.NET 9+).
* [SignalR Hub Protocol](https://github.com/dotnet/aspnetcore/blob/main/src/SignalR/docs/specs/HubProtocol.md)

3. Transports Section — Minor Clarity Improvement

File: aspnetcore/signalr/introduction.md
Location: Lines 36-44
Type: Minor enhancement

Current content:

## Transports

SignalR supports the following techniques for handling real-time communication (in order of graceful fallback):

* [WebSockets](xref:fundamentals/websockets)
* Server-Sent Events
* Long Polling

SignalR automatically chooses the best transport method that is within the capabilities of the server and client.

Suggested direction: Consider briefly noting that WebSockets is the preferred and most performant transport. This helps readers quickly understand the priority.

4. Missing Protocol Information

File: aspnetcore/signalr/introduction.md
Type: New paragraph

Suggested direction: The overview does not mention the two supported hub protocols: JSON (default) and MessagePack (binary, higher performance). For an overview article, a brief mention with a link to the MessagePack docs would be valuable.

5. Potentially Broken Training Module Link

File: aspnetcore/signalr/introduction.md
Location: Line 58
Type: Verify / Update

Current content:

* [Introduction to ASP.NET Core SignalR](/training/modules/aspnet-core-signalr)

Issue: This Microsoft Learn training module link may have been moved, renamed, or retired. Verify the link resolves correctly. If the module no longer exists, remove the link or replace with a current resource.

6. Scaling Mention Lacks Depth

File: aspnetcore/signalr/introduction.md
Location: Line 31
Type: Enhancement

Current content:

* Scales to handle increasing traffic.

Suggested direction: Consider briefly mentioning Azure SignalR Service or linking to the scale-out documentation, since "scales to handle increasing traffic" is vague without context on how scaling is achieved (e.g., Redis backplane, Azure SignalR Service).

7. Update ms.date Metadata

File: aspnetcore/signalr/introduction.md
Location: Line 8
Type: Metadata update

Current content:

ms.date: 12/02/2024

Suggested direction: Update to the date of the refresh PR.

🎯 Suggested Action Plan

For documentation team review

1. Remove or update the ES6 section:

   • Remove the [!INCLUDE[](~/includes/SignalR/es6.md)] reference at line 54.
   • Remove the ES6 link from Additional resources at line 63.
   • Consider whether es6.md include is used elsewhere; if not, remove the file.

2. Add .NET 9 features to feature list:

   • Navigate to lines 26-33.
   • Add bullet points for Native AOT, distributed tracing/diagnostics, and polymorphic hub methods.

3. Add hub protocol information:

   • Add a brief section or note about JSON (default) and MessagePack protocols.

4. Verify the training module link:

   • Check line 58 resolves correctly; update or remove as needed.

5. Enhance scaling bullet:

   • Add a link to scale-out docs or mention Azure SignalR Service at line 31.

6. Update ms.date at line 8.

⚠️ Review Considerations

• The .NET 10 release notes show an empty SignalR section — confirm there are no .NET 10-specific SignalR features that should be called out.
• Check if es6.md include is referenced by other articles before removing the file.
• Verify all xref links still resolve (e.g., xref:signalr/supported-platforms, xref:tutorials/signalr).

🔗 References

• Published article: https://learn.microsoft.com/en-us/aspnet/core/signalr/introduction?view=aspnetcore-10.0
• Source file: https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/signalr/introduction.md
• .NET 9 SignalR release notes: https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-9/includes/signalr.md
• .NET 10 release notes: https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-10.0.md