How can i inejct only one intance of my DbContext per request in my controllers?

Two (almost) concurrent DbContexts causing problems: How to share between Controller and AuthorizeAttribute

I had exactly the same issue when starting out with a base application using Entity Framework 6 for the first time. ...The best solution for me was to ensure only one DbContext instance during the request life cycle using Autofac (with MVC integration) and Autofac's InstancePerRequest lifetime scope....If you're interested in going down the depend...

Solutions with one EF6 model (db first) and one code first

Ok, got to the bottom of this. Basically if you share a connection across both contexts this does not work. However if you use a different connection for both it works....Thanks to Ben Robinson for pointing me in right direction.

Change the connection string dynamically (per request) on Entity Framework 7 / MVC 6

I would have preferred not to answer my own question, but I feel that I must offer guidance to those with a similar problem, after a long and deep research over internet so I can save them a lot of time testing multi-connection scenarios, wich is quite laborious......I've finally used a (very recent) feature and APIs of Azure called "Elastic Databa...

What way is better: make own wrapper for DbContext or use DbContext in Controller

The answer to your question is primarily opinion-based. No one can definitively say "one way is better than the other" until a lot of other questions are answered. What is the size / scope / budget of your project? How many developers will be working on it? Will it only have (view-based) MVC controllers, or will it have (data-based) API controllers...

Inject DbContext when database name is only know when the controller action is called

You can/should use an abstract factory to create the DbContext...public interface IDbContextFactory { ApplicationContext Create(); } public class DbContextFactory() : IDbContextFactory, IDisposable { private ApplicationContext context; private bool disposing; public DbContextFactory(/* other dependencies here */) { } ...

Structuremap - dependency injection - EF Core DBContext lifetime per request

Confirmed: the default lifetime is ...transient..., and with ...StructureMap... that means ...Per Request Lifetime.......If you want an app lifetime ...Singleton... you need to specify it....For<IDistributedTaskRepository>().Use<DistributedTaskRepository>().Singleton();

Create EF Core Context once per request in ASP.Net Core

base on ...What is new in EF Core 2.0 - EF Core | Microsoft Docs...If you want a new context once per request : AddDbContext...public void ConfigureServices(IServiceCollection services) { services.AddDbContext<MCContext >( options => options.UseSqlServer(connectionString)); } ...then you can ...public class TiketsController : ControllerBase ...

EF Core with DbContext pool and multi tenancy - database per tenant

Yes, you can use query filters ...No, you cannot use DbContext pooling

Entity Framework 6.2 copy many to many from one DbContext to another DbContext

First, don't use ...AsNoTracking...:...var courses = DbContextHDD.Courses. ... ...Second, ...Include... the required data:...var courses = DbContextHDD.Courses .Include(c => c.Students) .ToList(); ...Third, add the courses to the other context:...DbContextUSB.Courses.AddRange(courses); DbContextUSB.SaveChanges(); ...You may not believe it, ...

Is a DbContext per thread in Parallel.ForEach safe?

Issue #1 - Memory Allocation...Every single iteration will create instance of ...DbContext... which will lead to memory allocations. Garbage collector will need to deal with those allocations. If there will be constant memory pressure it will end up in performance degradation on application level....Issue #2 - SQL overload...Based on written above ...