From bc885f70bc5e4e97d606d332c7fbf9f9573b47a6 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 16 Apr 2026 14:49:00 -0500 Subject: [PATCH 1/2] Add a link to Not Found coverage --- aspnetcore/blazor/fundamentals/handle-errors.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/aspnetcore/blazor/fundamentals/handle-errors.md b/aspnetcore/blazor/fundamentals/handle-errors.md index 768e82ed11bc..0429678d2fa3 100644 --- a/aspnetcore/blazor/fundamentals/handle-errors.md +++ b/aspnetcore/blazor/fundamentals/handle-errors.md @@ -989,7 +989,18 @@ Consider manual render tree builder logic on the same level of complexity and wi ## Additional resources -:::moniker range=">= aspnetcore-8.0" +:::moniker range=">= aspnetcore-10.0" + +* [Handle caught exceptions outside of a Razor component's lifecycle](xref:blazor/components/sync-context#handle-caught-exceptions-outside-of-a-razor-components-lifecycle) +* [Not Found responses](xref:blazor/fundamentals/navigation#not-found-responses) +* +* † +* +* [Blazor samples GitHub repository (`dotnet/blazor-samples`)](https://github.com/dotnet/blazor-samples) ([how to download](xref:blazor/fundamentals/index#sample-apps)) + +:::moniker-end + +:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0" * [Handle caught exceptions outside of a Razor component's lifecycle](xref:blazor/components/sync-context#handle-caught-exceptions-outside-of-a-razor-components-lifecycle) * From 641c5cc987d89c9b8df4f3d7a6f0b9e91439951f Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Thu, 16 Apr 2026 19:03:07 -0500 Subject: [PATCH 2/2] Fix grammar in handle-errors.md --- aspnetcore/blazor/fundamentals/handle-errors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/blazor/fundamentals/handle-errors.md b/aspnetcore/blazor/fundamentals/handle-errors.md index 0429678d2fa3..a14643a7af90 100644 --- a/aspnetcore/blazor/fundamentals/handle-errors.md +++ b/aspnetcore/blazor/fundamentals/handle-errors.md @@ -964,7 +964,7 @@ Infinite loops during rendering: * Causes the rendering process to continue forever. * Is equivalent to creating an unterminated loop. -In these scenarios, the Blazor fails and usually attempts to: +In these scenarios, Blazor fails and usually attempts to: * Consume as much CPU time as permitted by the operating system, indefinitely. * Consume an unlimited amount of memory. Consuming unlimited memory is equivalent to the scenario where an unterminated loop adds entries to a collection on every iteration.