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
We've received feedback from users that the component code generated by the Blazor CRUD scaffolder should use the IDbContextFactory instead of injecting the DbContext directly to avoid making multiple overlapping queries with the same DbContext instance. With static server-side rendering this is less likely to happen, but we think it's best to make the change to be in line with our documented Blazor guidance.
The text was updated successfully, but these errors were encountered:
I'm working on a new Pluralsight course called "Building a Data-driven Blazor Server Application with EF Core" and while recording the demo of the scaffolder I just noticed that the generated code is using IDbContextFactory. That's fantastic! Thank you everyone!
We've received feedback from users that the component code generated by the Blazor CRUD scaffolder should use the
IDbContextFactory
instead of injecting theDbContext
directly to avoid making multiple overlapping queries with the sameDbContext
instance. With static server-side rendering this is less likely to happen, but we think it's best to make the change to be in line with our documented Blazor guidance.The text was updated successfully, but these errors were encountered: