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

ZZZ_tmp

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

Okay, let's resolve this. In essence, this is impossible if a relationship is shared between the two contexts. However, it functions if you use a different connection for both....I appreciate Ben Robinson's help in directing me in the proper way.

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

ZZZ_tmp

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

ZZZ_tmp

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

ZZZ_tmp

Structuremap - dependency injection - EF Core DBContext lifetime per request

ZZZ_tmp

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

ZZZ_tmp

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

ZZZ_tmp

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

ZZZ_tmp

Is a DbContext per thread in Parallel.ForEach safe?

First Problem: Memory Allocation...Each iteration will produce an instance of...DbContext... This will result in the allocation of RAM. Those allocations must be handled by the garbage collector. The performance of the program will suffer if memory is always under demand....Second problem: SQL overload...Based on the information provided here, you ...