Skip to content
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions aspnetcore/migration/fx-to-core/inc/blazor.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,12 @@ description: Learn how to enable ASP.NET Core Blazor Server support with Yarp in
monikerRange: '>= aspnetcore-6.0 < aspnetcore-8.0'
ms.author: tasou
ms.custom: "mvc"
ms.date: 07/17/2025
ms.date: 09/04/2025
uid: migration/fx-to-core/inc/blazor
---
# Enable ASP.NET Core Blazor Server support with Yarp in incremental migration

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.
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.

Add the following route builder extensions class to the project.

Expand Down