Currently, in the both the Web API and MVC frameworks, dependency injection support does not come into play until after the OWIN pipeline has started executing. This is simply a result of the OWIN support being added to both frameworks after their initial release. In fact, the OWIN support in MVC does not yet extend to the self hosting scenario and is limited to plugging in OWIN middleware.

I had two primary objectives when creating these new OWIN packages for Autofac:

  • Extend the Autofac lifetime scope from the OWIN pipeline into the MVC and Web API integrations
  • Make dependency injection avaialable to OWIN middleware components

Due to the somewhat fragmented nature of the DI support in the ASP.NET stack, achieving this goal required a bit of trickery and black magic. For that reason the packages are currently pre-release and marked as alpha. Hopefully you can pull them from NuGet and help test them out.

Enabling DI for OWIN middleware

Lets start with a service interface for a logging dependency...

public interface ILogger
{
void Write(string message, params object[] args);
}

...along with its rather unimaginative implementation (just imagine something more interesting).

public class Logger : ILogger
{
public void Write(string message, params object[] args)
{
Debug.WriteLine(message, args);
}
}

To enable dependency injection for OWIN middleware derive from OwinMiddleware as usual, and add any additional constructor dependencies after the constructor parameter for the next middleware in the chain. In the example below we are adding the ILogger dependency to the middleware.

public class LoggerMiddleware : OwinMiddleware
{
private readonly ILogger _logger; public LoggerMiddleware(OwinMiddleware next, ILogger logger) : base(next)
{
_logger = logger;
} public override async Task Invoke(IOwinContext context)
{
_logger.Write("Inside the 'Invoke' method of the 'LoggerMiddleware' middleware."); foreach (var pair in context.Environment)
_logger.Write("Key: {0}, Value: {1}", pair.Key, pair.Value); await Next.Invoke(context);
}
}

To wire this up we have to register the middleware and its dependencies with the container, and then enable the middleware dependency injection support via a call to UseAutofacMiddleware. This call should be the first piece of middleware registered with the IAppBuilder.

var builder = new ContainerBuilder();

builder.RegisterType<LoggerMiddleware>().InstancePerApiRequest();
builder.Register(c => new Logger()).As<ILogger>().InstancePerLifetimeScope(); app.UseAutofacMiddleware(container);

This particular extension method is included in the Autofac.Owin package which is shared by the Autofac.WebApi2.Owin and Autofac.Mvc5.Owin packages. You would not normally use this package by itself because of the second role the shared package plays. Not only is it responsible for adding middleware dependency injection support, it also creates an Autofac ILifetimeScope instance for each request early in the OWIN pipeline. You can access this lifetime scope using the GetAutofacLifetimeScope method on IOwinContext. The OWIN packages for the Web API and MVC integrations use this method to access the lifetime scope and make it available further along in the request.

Extending the lifetime scope to Web API

To enable the lifetime scope created during the OWIN request to extend into the Web API dependency scope call the UseAutofacWebApi method.

app.UseAutofacMiddleware(container);
app.UseAutofacWebApi(GlobalConfiguration.Configuration);

This will add a DelegatingHandler which extracts the ILifetimeScope from the IOwinContext. Once it has a hold of the ILifetimeScope an AutofacWebApiDependencyScope is created and added into the appropriate HttpRequestMessage property that Web API expects the IDependencyScope to be available from. The code below shows this task being performed during the SendAsync method of the handler.

protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
{
if (request == null) throw new ArgumentNullException("request"); var owinContext = request.GetOwinContext();
if (owinContext == null) return base.SendAsync(request, cancellationToken); var lifetimeScope = owinContext.GetAutofacLifetimeScope();
if (lifetimeScope == null) return base.SendAsync(request, cancellationToken); var dependencyScope = new AutofacWebApiDependencyScope(lifetimeScope);
request.Properties[HttpPropertyKeys.DependencyScope] = dependencyScope; return base.SendAsync(request, cancellationToken);
}

Notice that we still made a call to UseAutofacMiddleware. This is required because along with enabling the middleware DI support, this is also responsible for placing the lifetime scope in the OWIN context. I'm not totally happy with this dual responsibility but it does reduce the API surface area and means less IAppBuilder extensions are required. For now, if you don't want to use middleware DI support, don't register your middleware with the container.

Extending the lifetime scope to MVC

To enable the lifetime scope created during the OWIN request to extend into the MVC request call the UseAutofacMvc method on your IAppBuilder instance.

app.UseAutofacMiddleware(container);
app.UseAutofacMvc();

Just like with Web API we need to ensure that UseAutofacMiddleware has been called first. You only need to call this method once, even when using both the MVC and Web API integrations together. Remember, the call to UseAutofacMiddleware should be made as early as possible during the bootstrapping process.

In the MVC middleware we are also retrieving the ILifetimeScope from the IOwinContext, but in this case we are placing it in the HttpContext as is expected by the MVC integration. The code below shows this process directly implemented in a middleware method.

public static IAppBuilder UseAutofacMvc(this IAppBuilder app)
{
return app.Use(async (context, next) =>
{
var lifetimeScope = context.GetAutofacLifetimeScope();
var httpContext = CurrentHttpContext(); if (lifetimeScope != null && httpContext != null)
httpContext.Items[typeof(ILifetimeScope)] = lifetimeScope; await next();
});
}

In case you are wondering, CurrentHttpContext is an internal property that returns a HttpContextBase allowing for mocking of the HTTP context during unit testing.

NuGet Packages

As mentioned earlier the packages are currently pre-release, so don't forget the -Preswitch on the command line, or the Include Prerelease option in the GUI. Please report any issues that you find on GitHub.

Autofac Web API OWIN Integration:

Install-Package Autofac.WebApi2.Owin -Pre

Autofac MVC 5 OWIN Integration:

Install-Package Autofac.Mvc5.Owin -Pre

Please note that you still need to configure the relevant dependency resolver for each integration: AutofacWebApiDependencyResolver for Web API, and AutofacDependencyResolverfor MVC.

OWIN support for the Web API 2 and MVC 5 integrations in Autofac的更多相关文章

  1. 使用 OWIN 作为 ASP.NET Web API 的宿主

    使用 OWIN 作为 ASP.NET Web API 的宿主 ASP.NET Web API 是一种框架,用于轻松构建可以访问多种客户端(包括浏览器和移动 设备)的 HTTP 服务. ASP.NET ...

  2. 使用 OWIN Self-Host ASP.NET Web API 2

    Open Web Interface for .NET (OWIN)在Web服务器和Web应用程序之间建立一个抽象层.OWIN将网页应用程序从网页服务器分离出来,然后将应用程序托管于OWIN的程序而离 ...

  3. ASP.NET Web API - ASP.NET MVC 4 系列

           Web API 项目是 Windows 通信接口(Windows Communication Foundation,WCF)团队及其用户激情下的产物,他们想与 HTTP 深度整合.WCF ...

  4. web api .net C# mvc API返回XML文档的解析并取值

    [HttpGet] public System.Net.Http.HttpResponseMessage GetNotify() { var xmlstring = @" <xml&g ...

  5. 购物车Demo,前端使用AngularJS,后端使用ASP.NET Web API(3)--Idetity,OWIN前后端验证

    原文:购物车Demo,前端使用AngularJS,后端使用ASP.NET Web API(3)--Idetity,OWIN前后端验证 chsakell分享了前端使用AngularJS,后端使用ASP. ...

  6. Use OWIN to Self-Host ASP.NET Web API 2

      Open Web Interface for .NET (OWIN)在Web服务器和Web应用程序之间建立一个抽象层.OWIN将网页应用程序从网页服务器分离出来,然后将应用程序托管于OWIN的程序 ...

  7. CORS support for ASP.NET Web API (转载)

    CORS support for ASP.NET Web API Overview Cross-origin resource sharing (CORS) is a standard that al ...

  8. Asp.Net Web API VS Asp.Net MVC

    http://www.dotnet-tricks.com/Tutorial/webapi/Y95G050413-Difference-between-ASP.NET-MVC-and-ASP.NET-W ...

  9. 关于 Web Api 2 认证与授权

    认证与授权 认证与授权,Authentication and Authorize,这个是两个不同的事.认证是对访问身份进行确认,如验证用户名和密码,而授权是在认证之后,判断是否具有权限进行某操作,如 ...

随机推荐

  1. JDK历史版本下载

    JDK6: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409. ...

  2. 100722B

    在stack里套set,然后每次根据他的操作,在set里操作,把括号hash,插入,输出set的size-1 #include<iostream> #include<set> ...

  3. windows系统激活-使用微软官方公布的kms client setup key安装或安装后使用slmgr导入

    windows 10各版本: Windows 10 Professional W269N-WFGWX-YVC9B-4J6C9-T83GX Windows 10 Professional N MH37W ...

  4. mysql-查看全局变量设置

    show global variables like '%sql_mode%' 全局变量

  5. C#-WinForm-打开其他窗体的三种方式-Show()、设置Owner()、ShowDialog()

    打开其他窗体的三种方式 Show - 例如登入界面进入主页面,直接将主页面展示出来,两个窗体互不影响 public partial class Form1 : Form { public Form1( ...

  6. Linq Like

    Like的操作,有点像in,但是,方向变了.什么意思呢.就是你给定一个字符串,去寻找数据中某个字段包含这个字符串.就是给定的字符串是某字段的子集.Sql Script是这么写的. Selec * fr ...

  7. Android成长日记-ViewPager的使用

    ViewPager在安卓应用中主要用于作为程序的引导页面,欢迎页面,以及其他的动画效果,下面将给你讲述ViewPager的使用 在Android3.0以上的Api中,提供了ViewPager的接口,所 ...

  8. linux下制作win7安装盘(mint、ubuntu、debian)

    今天替同事装系统.因为现在的debian系系统都可以直接用dd拷贝iso到u盘的方法进行安装,所以,想当然的用dd来制作windows安装盘.没反应!所以有了下面的方法. 1. 将u盘格式化为ntfs ...

  9. Error: cannot find a valid baseurl for repo: rpmfusion-free 解决办法

    今天在玩CentOS的时候出现了: Error: cannot find a valid baseurl for repo: rpmfusion-free 这个问题真到好恶心啊,以前一直使用到是ubu ...

  10. select 1 from dual 中的1表示的含义

    select 1 from dual   在这条sql语句中的1代表什么意思?查出来是个什么结果?   其实: select 1 from table; select anycol(目的表集合中的任意 ...