You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a server-interactive page in Blazor 8, the ApplicationContextAccessor will sometimes pick the aspnetcore IContextManager when it should use the Blazor server context manager.
The constructor needs to walk backwards through the list of registered IContextManager services so it selects the one that is valid and is also the most recently added to the list.
varmanagers= contextManagerList.ToList();for(inti= managers.Count -1;i >= 0;i--){if(managers[i].IsValid){ContextManager= managers[i];break;}}ContextManager ??= new Core.ApplicationContextManagerAsyncLocal();
The text was updated successfully, but these errors were encountered:
In a server-interactive page in Blazor 8, the
ApplicationContextAccessor
will sometimes pick the aspnetcoreIContextManager
when it should use the Blazor server context manager.The constructor needs to walk backwards through the list of registered
IContextManager
services so it selects the one that is valid and is also the most recently added to the list.The text was updated successfully, but these errors were encountered: