实体框架核心1.0 DbContext不限于http请求

本文介绍了实体框架核心1.0 DbContext不限于http请求的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

通过与罗文·米勒一起观看此视频，我了解了 https://channel9.msdn.com/Series/Whats- ASPNET-5/06的新功能(第22分钟)在Startup.cs中将Entity Framework Core(以前称为EF7)配置为ASP.NET Core 1.0应用(以前称为ASP.NET 5)的方式如下:

I understood by watching this video with Rowan Millerhttps://channel9.msdn.com/Series/Whats-New-with-ASPNET-5/06(at minute 22)that the way of configuring Entity Framework Core (previously known as EF7) into an ASP.NET Core 1.0 app (previously known as ASP.NET 5) in Startup.cs is as follows:

    public void ConfigureServices(IServiceCollection services)
    {
        //Entity Framework 7 scoped per request??
        services.AddEntityFramework()
            .AddSqlServer()
            .AddDbContext<MyDbContext>(options =>
            {
                options
                  .UseSqlServer(Configuration["Data:DefaultConnection:ConnectionString"]);
            });

        //MVC 6
        services.AddMvc();
    }

，并且此DbContext的作用域将是一个http请求，这样，无论何时在整个http管道(包括中间件或MVC)的代码中使用DbContext，我们都可以肯定知道实例已注入DI容器上的相同.

and that this DbContext will be scoped to an http request so that whenever in the code throughout the http pipeline (including middleware or MVC) a DbContext is used, we know for sure that the instance injected by the DI container will be the same.

但是问题在于它似乎无法以这种方式工作.在MVC的生命周期内，确实注入的DbContext实例是相同的，但如下所述:我正在尝试将以下中间件插入管道中，以在控制器完成执行后实现某种集中式的Commit/Rollback:

But the problem is that it does not seem to work that way. Within the lifetime of MVC it is true that the DbContext instance injected is the same, but as described here: Entity Framework Core 1.0 unit of work with Asp.Net Core middleware or Mvc filterI am trying to plug into the pipeline the following middleware to achieve some kind of centralised Commit/Rollback after a controller finalises execution:

public class UnitOfWorkMiddleware
{
    private readonly RequestDelegate _next;
    private readonly MyDbContext _dbContext;
    private readonly ILogger _logger;

    public UnitOfWorkMiddleware(RequestDelegate next, MyDbContext dbContext, ILoggerFactory loggerFactory)
    {
        _next = next;
        _dbContext = dbContext;
        _logger = loggerFactory.CreateLogger<UnitOfWorkMiddleware>();
    }

    public async Task Invoke(HttpContext httpContext)
    {
        await _next.Invoke(httpContext);
        _logger.LogInformation("Saving changes for unit of work if everything went good");
        await _dbContext.SaveChangesAsync();
    }
}

并且该中间件比管道中的MVC6早得多

and this middleware is immediately before than MVC6 in the pipeline

//inside Configure(IApplicationBuilder app) in Startup.cs
app.UseMiddleware<UnitOfWorkMiddleware>();
app.UseMvcWithDefaultRoute();

中间件中的DbContext实例与MVC生命周期中注入的实例不同.

这是预期的吗?不应将DbContext限制为http请求吗?可以实现我试图实现的目标吗?

Is this expected? Shouldn't a DbContext be scoped to an http request? Is possible to achieve what I was trying to achieve?

计划B将使用 MVC 6全局过滤器(如果我可以找到一些有关如何执行此操作的文档).我假设作为MVC 6框架的一部分，注入的DbContext实例将是相同的.

The plan B would be to use an MVC 6 Global filter (if I can find some documentation on how to do this). I assume that being part of MVC 6 framework, the DbContext instance injected will be the same..

achieve

实体框架核心1.0 DbContext不限于http请求

问题描述

推荐答案