Blazor migration guidance 8.0

[guardrex]

Fixes #29505
Fixes #30471
Fixes #29522

Ready for review!

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/components/integration.md	Integrate ASP.NET Core Razor components into ASP.NET Core apps
aspnetcore/migration/70-80.md	[Visual Studio Code](https://review.learn.microsoft.com/en-us/aspnet/core/migration/70-80?branch=pr-en-us-30671)
aspnetcore/release-notes/aspnetcore-8.0.md	What's new in ASP.NET Core 8.0

[guardrex]

@robertmclaws ... Standalone WASM doesn't require more than the first three main doc updates (global.json, framework, packages), and there's a short section to call that out now.

There's hosted WASM guidance now. I only just typed it out this morning ... and it's missing some content for guidance on prerendered components ... and there are bound to be some 😈😈😈 in it.

We'll iron out the coverage shortly ... today ... tomorrow ... soon 🏃😅.

WRT your remark ...

create a new app and copy the code over

If you want every bleed'in update 😆 ... then Yes! That's the guidance, and it probably always will be the guidance. Only once did I write out every single line change required for an update (back for the 5.0 release), and it was a 😈 living daymare 😈 to write, follow, and maintain ... perfect for 🎃 Halloween 🧟‍♂️! 😆 I don't think we'll ever try to do that again. Make a new project, move the bits ... components/pages with mods for new features ... update the layout/styles ... 🎤 drop ... Done! 😄 That's our recommendation for devs who want every little update that was made for project templates.

As for adding some additional changes to the scenarios on the PR, Yes! We're going to take a look at that right now on review. What's on the PR are the minimum steps required to update to 8.0, making it possible to then adopt the new 8.0 features. We'll see if there's anything else that DR and Artak would like to add to the steps taking the resultant app closer to a BWA. Stand-by for their reviews ...........................

[danroth27]

Can we split the integration article updates into a separate PR so we can get the migration content merged in? The migration content looks pretty much ready to go, but I want to work on the integration content some more.

[guardrex]

split the integration article updates into a separate PR

Yes, I'll press the Easy button on that and merely comment out the new content in the Integration article. I'll wrap this up now and open a new PR, where we can pick back up with the coverage.

[shrayasr]

@guardrex : please forgive me if this isn't the right place to voice this, but given that this PR is the one that made the migration, I thought it best to write here.

Allow me to set some context first. We are heavily invested in Blazor but we had to take a pause because of the incomplete auth story. I tweeted this out and @danroth27 kindly responded asking me to check if it was fixed in NET8. And it has been! So we're back on the Blazor bandwagon now.

However while we were upgrading, we saw the following suggestion

- app.MapBlazorHub();
+app.MapRazorComponents<App>()
+   .AddInteractiveServerRenderMode()

And we're kind of stuck here since our previous call to MapBlazorHub looked like this:

endpoints.MapBlazorHub(config =>
{
    config.CloseOnAuthenticationExpiration = true;
});

And we're unable to find out where we should be moving the CloseOnAuthenticationExpiration call to?

Is this something that you're able to help us with?

Cheers and thanks for all the great work!

[guardrex]

@shrayasr ... Open a new issue from the bottom of the Migration article because you have raised an excellent point about passing configuration options to the extension methods. I agree that we need coverage.

I recommend titling the issue:

Add Blazor migration guidance on service/endpoint configuration

For the text, copy and paste the remarks you just made into the opening comment.

[shrayasr]

Thanks for the super fast response @guardrex. I have done as per your advise. Issue is here: #30843