Configuring Dbcontext as Transient
In ASP.NET Core / EntityFramework Core, the services.AddDbContext<> method will add the specified context as a scoped service. It's my understanding that that is the suggested lifetime management for the dbcontext by Microsoft.
However, there is much debate in our engineer department over this and many feel that the context needs to be disposed of ASAP. So, what is the best way to configure the dbcontext as Transient that still maintains the same Repository pattern typically used (i.e. injecting the context directly into the repository's constructor) as well as supporting flexible unit testing?
using(var context = transientDbContextFactory.Create()) { ... } for the cases where you need the transient context and keep it at scoped for rest of your application.
The lifetime is a parameter on AddDbContext<>(). See example:
services.AddDbContext<ApplicationDbContext>(options =>
options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")),
ServiceLifetime.Transient);
This will add it to the service collection with transient lifetime.
In my opinion, a good use case for registering a DbContext as a transient dependency is within worker services that are registered as singletons. You can not use scoped dependencies within singleton dependencies. So the only option you have is to register the DbContext as either singleton or transient. Something to bear in mind is that the injected DbContextOptions class lifetime also needs to be updated. You can do both by specifying the service lifetime as follows.
services.AddDbContext<DataContext>(options =>
{
options.UseMySQL(configurationRoot.GetConnectionString("DefaultConnection"));
options.UseLazyLoadingProxies();
}, ServiceLifetime.Transient, ServiceLifetime.Transient);
The third parameter is for the service lifetime of the DbContextOptions instance.
You can also create a repository class and interface which has idbcontext constructor parameter. Have all of your controller constructors use this interface in their constructor. This can be added with addtransient. This way, Microsoft still controls the dbcontext as it sees fit. Context will be managed by runtime and injected when creating repository instances when creating controllers.
Follow WeChat
Success story sharing
Func<T>), or always create a new child scope everywhere you're resolving the DbContext. So the first rule of thumb is usually the simplest: just don't use transient.