I am using Blazor COMPONENTS mixed in with my .NET MVC app. I'm slowly porting over away from MVC and into full blazor. The problem I have is, because we have a persistent blazor server connection, it's a long-standing "request" which means it holds on to DB connections. IF a transaction is in flight, until the Blazor server connection is severed, the DB is locked to other pages! I'm currently getting around it by creating a new scope on every request and not injecting any services into my blazor component and instead resolving them at runtime in each method handler. Is that really the only solution? Or is there some way to set this up that it works properly with Blazor server?
I've searched around and haven't been able to find anything in the documentation that might point me in the right direction.
