Skip to content

Commit 3c08a62

Browse files
authored
Add .NET 8 fix cross-link (#36050)
1 parent 772e1c5 commit 3c08a62

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

aspnetcore/migration/fx-to-core/inc/blazor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ description: Learn how to enable ASP.NET Core Blazor Server support with Yarp in
55
monikerRange: '>= aspnetcore-6.0 < aspnetcore-8.0'
66
ms.author: tasou
77
ms.custom: "mvc"
8-
ms.date: 07/17/2025
8+
ms.date: 09/04/2025
99
uid: migration/fx-to-core/inc/blazor
1010
---
1111
# Enable ASP.NET Core Blazor Server support with Yarp in incremental migration
1212

13-
When adding Yarp to a Blazor Server app, both attempt to act as fallback routes for the app's request routing. Either Blazor or Yarp handles routing arbitrarily, which means that scenarios such as deep linking in Blazor may fail. This will be fixed in the .NET 8 release later this year. For migration to ASP.NET Core in .NET 6 and .NET 7, map Blazor's endpoints to achieve correct request routing by following the guidance in this article.
13+
When adding Yarp to a Blazor Server app, both attempt to act as fallback routes for the app's request routing. Either Blazor or Yarp handles routing arbitrarily, which means that scenarios such as deep linking in Blazor may fail. This is [fixed in .NET 8](xref:migration/70-to-80#drop-blazor-server-with-yarp-routing-workaround). For migration to ASP.NET Core in .NET 6 and .NET 7, map Blazor's endpoints to achieve correct request routing by following the guidance in this article.
1414

1515
Add the following route builder extensions class to the project.
1616

0 commit comments

Comments
 (0)