.NET 8 Blazor - DbContextFactory and EF Core Lazy Loading about aspnetcore

[mkArtakMSFT]

Thanks for bringing this up, @sbwalker.
Have you seen my response in #54539 (comment)? Maybe that addresses this too?

[sbwalker]

@mkArtakMSFT I don't think it does address the issue. I am developing Static Server-Side components and when I use EF Core for data access I was running into exceptions:

"System.InvalidOperationException: There is already an open DataReader associated with this Connection which must be closed first."

I consulted the documentation which mentions "server-side Blazor apps":

"In server-side Blazor apps, DbContext isn't thread safe and isn't designed for concurrent use. The existing lifetimes are inappropriate for these reasons:

1. Singleton shares state across all users of the app and leads to inappropriate concurrent use.
2. Scoped (the default) poses a similar issue between components for the same user.
3. Transient results in a new instance per request; but as components can be long-lived, this results in a longer-lived context than may be intended.

By default, consider using one context per operation. The context is designed for fast, low overhead instantiation:

using var context = new MyContext();
return await context.MyEntities.ToListAsync();"

So I modified my code to use DbContextFactory and it fully resolved my issue.

So in my experience DbContextFactory needs to be used in Static Server-Side Blazor as well as Interactive - Blazor Server scenarios.