I ran into problems using a DbContext with Blazor components using InteractiveServer render mode, so now I have to change all injections of my DbContext into a IDbContextFactory<T>. Fun times... - ThreadSky

About ThreadSky

patriksvensson.se • 88 days ago

I ran into problems using a DbContext with Blazor components using InteractiveServer render mode, so now I have to change all injections of my DbContext into a IDbContextFactory. Fun times...

Comments

amoerie.bsky.social•87 days ago

I've been encapsulating EF usage with a DbContextProvider interface for ages now, and it hasn't failed me yet. I find recommending the injection of DbContext everywhere as the default approach a terrible decision on the EF team's part, too many footguns.

dunnhq.com•87 days ago

I use mediator for commands that take part in a unit of work flow. Actually works quite nicely

patriksvensson.se•87 days ago

I do as well, but that doesn't help that scenario.

dunnhq.com•87 days ago

It helped me by having the scope be from the Inception of the command and shared amongst all the handlers. It also meant I could get rid of repositories which I've never been a fan of

patriksvensson.se•87 days ago

Problem with Blazor interactive server rendering is that the scope is really long lived (think potential hours), so you cannot rely on the DI framework.