Consider registering the authentication state provider conditionally

[javiercn]

Use TryAddScoped here instead of AddScoped

aspnetcore/src/Components/Server/src/DependencyInjection/ComponentServiceCollectionExtensions.cs

Line 82 in 02e7e14

services.AddScoped<AuthenticationStateProvider, ServerAuthenticationStateProvider>();

It's not clear to me why we do this, but I suspect that it is because in the past we might have had a different implementation registered by default inside MVC for rendering components statically.

I don't believe we need this any longer and it creates a hard to debug issue for our customers as it forces an order when customers want to provide a custom implementation (on something that we tell customers to customize).

I can't foresee any drawback on changing this to use TryAddScoped instead, so we should do so.

[javiercn]

This issue came as a result of looking into #41228

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[damienbod]

Hi @javiercn I could try this one if you want, I would like to look the Blazor authentication anyway.