ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A practical guide to Transient, Scoped, and Singleton lifetimes in .NET's built-in DI container, with a runnable example showing how to observe instance identity across requests and why captive dependencies slip through in Production.
Learn how to register and verify Transient, Scoped, and Singleton services in .NET Core, avoid common pitfalls, and ensure correct lifetime behavior with concrete examples and diagnostics.
Use .NET Core DI lifetimes as trust boundaries. Keep DbContext Scoped per request, avoid captive dependencies with Singleton services, and create explicit scopes for background work. Validate with ValidateScopes and scope identity tests.
Misregistering service lifetimes can cause state leaks or startup crashes; this post shows how to verify and avoid common DI pitfalls in ASP.NET Core.
Entity Framework Core DbContext pooling, introduced in version 5.0, reuses context instances across requests to reduce allocation overhead. Production environments commonly enable pooling via service configuration, while local development often defaults to disabled or in-memory providers, obscuring state-related side effects. When pooling is active, change-t
entityframeworkcore