Need way to disable disposing of DbContext when root DbContextScope is disposed about dbcontextscope HOT 3 CLOSED

In short words, the answer is: register your DbContext as Transient lifetime.

And ... the long story:
In .NET Core 1.1 you register your DbContexts by default in Scoped lifetime, like this:
services.AddDbContext<AttendeeContext>(options => options.UseSqlServer(connectionString)

So, how DbContextScope does his job (as long, as I debugged sources):

1. in each new scope, (like it usually recommends: using (var dbScope = _factory.Create()) { ... } ) the new collection of DbContexts initialized - not previously initialized DbContexts in the current scope of whole web request.
2. when the dbScope code block ends, using statement calls Dispose for your DbContextScope and that means exact disposing of all your existing collection of DbContexts.
3. What does it mean for lifetime of DbContext in scope of lifetime of whole Web request?
   -- it means, that you manually have killed DbContext somewhere in the middle of living your Web request, and DbContext becomes unavailable for next calls inside still alive Web Request.

The solution is to allow your serviceProvider to recreate DbContext for each request during Scoped lifetime of your Web request:
services.AddDbContext<AttendeeContext>(options => options.UseSqlServer(connectionString, ServiceLifeTime.Transient)
And by the way, I also registered IDbContextScopeFactory as Singleton lifetime.

from dbcontextscope.

Can you just not dispose the DbContextScope?

from dbcontextscope.

Jaap-van-Hengstum, please, share your decision, if your figured it out. I'm really on the same page with about this question.
I play with .NET Core and native DI for my Web API. Tried many approches with DbContextScope , IAmbientContextLocator and their lifetimes. As I understood correctly, DbContextScope should be Transient and AmbientContextLocator - Singleton. But the problem exactly the same - DbContextScope kills DbContext everytime.

from dbcontextscope.