.NET & C# · Entity Framework Core
What is a common mistake with DbContext and DbSet in Entity Framework Core?
Keeping one DbContext alive too long can grow the change tracker, retain stale entities, and create concurrency problems.
Keeping one DbContext alive too long can grow the change tracker, retain stale entities, and create concurrency problems.