Add support for migrating using Blazor

[danroth27]

Cocoon Offers support for migrating ASP.NET projects using Blazor. This is appealing for ASP.NET Web Form developers that are used to a component-based event-driven programming model.

Cocoon does some clever things to enable migration with Blazor using the strangler-fig pattern, like collecting the routable components in the app so that the fallback to the ASP.NET app happens correctly.

[slipgateio]

I'd like to see Blazor added as well.

[Michelh91]

Yeah would be amazing if support to Blazor is added, fallback to page components not working now

[tbertenshaw]

Would be keen to see this!. Looking to migrate a .NET MVC/WebApi/Angular/AspNet Identity app hosted in Azure app Service, to blazor web assembly running in AKS

[gerneio]

Anyone successfully setup systemweb-adapters w/ Blazor? I know Cocoon has a sample using their tooling (as mentioned by @danroth27), however would be nice for the officially supported migration tooling to at least document a route for this, even if manual. Blazor is 100% our future and the only compelling reason for us migrate from web froms/framework to core.

[danroth27]

Blocked on dotnet/aspnetcore#42003

[joperezr]

As part of this, we will want to also add a doc into the migration documentation here

[joperezr]

related: dotnet/aspnetcore#42003

[twsouthwick]

This will be a part of ASP.NET Core 8, so for now we've added documentation here to enable support in ASP.NET Core 6 & 7: dotnet/AspNetCore.Docs#28535

[gerneio]

Very nice, thanks for getting this doc put together @twsouthwick!

Live link for others: Enabling Blazor support with Yarp