Add Blazor migration guidance on service/endpoint configuration

[shrayasr]

Description

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!

Page URL

https://learn.microsoft.com/en-us/aspnet/core/migration/70-80?view=aspnetcore-7.0&tabs=visual-studio

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/migration/70-80.md

Document ID

534ab561-09c5-c33b-4394-0effba34d666

Article author

Rick-Anderson

[guardrex]

Thanks for moving it over to this issue.

Yes! I totally agree ... and I ran into this exact scenario working on the reference docs. IIRC, I was working on updating the SignalR docs where hub config was shifting over based on the new extension methods. I couldn't find some optons but came to learn that they would appear in the next preview. Indeed, they arrived, and you can see the final result in this section ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/signalr?view=aspnetcore-8.0#server-side-circuit-handler-options

WRT to the auth question that you're asking, I might need to ping Jeremy to ask (or Steven Halter), as they're handling a certain amount of the auth updates this time around. However, I might be able to sort it out on my own.

I'm wrapping up a Blazor Forms article PR this morning, and I'll see if I can resolve this issue today. My plan in the non-auth cases is to cross-link to the new guidance (e.g., link to that SignalR options section from the Migration topic for SignalR hub config). We can't do that yet for auth options or setup because auth content hasn't been produced yet. What I'll do for anything I discover today on auth is call it out in the topic with examples there for the time being.

I'll get back to you later today.