Autofac is always kept up to date to support the latest version of ASP.NET MVC, so documentation is also kept up with the latest. Generally speaking, the integration remains fairly consistent across versions.

MVC integration requires the Autofac.Mvc5 NuGet package.

MVC integration provides dependency injection integration for controllers, model binders, action filters, and views. It also adds per-request lifetime support.

This page explains ASP.NET classic MVC integration. If you are using ASP.NET Core, see the ASP.NET Core integration page.

Quick Start

To get Autofac integrated with MVC you need to reference the MVC integration NuGet package, register your controllers, and set the dependency resolver. You can optionally enable other features as well.

protected void Application_Start()
  var builder = new ContainerBuilder();

  // Register your MVC controllers. (MvcApplication is the name of
  // the class in Global.asax.)

  // OPTIONAL: Register model binders that require DI.

  // OPTIONAL: Register web abstractions like HttpContextBase.

  // OPTIONAL: Enable property injection in view pages.
  builder.RegisterSource(new ViewRegistrationSource());

  // OPTIONAL: Enable property injection into action filters.

  // OPTIONAL: Enable action method parameter injection (RARE).

  // Set the dependency resolver to be Autofac.
  var container = builder.Build();
  DependencyResolver.SetResolver(new AutofacDependencyResolver(container));

The sections below go into further detail about what each of these features do and how to use them.

Register Controllers

At application startup, while building your Autofac container, you should register your MVC controllers and their dependencies. This typically happens in an OWIN startup class or in the Application_Start method in Global.asax.

var builder = new ContainerBuilder();

// You can register controllers all at once using assembly scanning...

// ...or you can register individual controlllers manually.

Note that ASP.NET MVC requests controllers by their concrete types, so registering them As<IController>() is incorrect. Also, if you register controllers manually and choose to specify lifetimes, you must register them as InstancePerDependency() or InstancePerRequest() - ASP.NET MVC will throw an exception if you try to reuse a controller instance for multiple requests.

Set the Dependency Resolver

After building your container pass it into a new instance of the AutofacDependencyResolver class. Use the static DependencyResolver.SetResolver method to let ASP.NET MVC know that it should locate services using the AutofacDependencyResolver. This is Autofac’s implementation of the IDependencyResolver interface.

var container = builder.Build();
DependencyResolver.SetResolver(new AutofacDependencyResolver(container));

Register Model Binders

An optional step you can take is to enable dependency injection for model binders. Similar to controllers, model binders (classes that implement IModelBinder) can be registered in the container at application startup. You can do this with the RegisterModelBinders() method. You must also remember to register the AutofacModelBinderProvider using the RegisterModelBinderProvider() extension method. This is Autofac’s implementation of the IModelBinderProvider interface.


Because the RegisterModelBinders() extension method uses assembly scanning to add the model binders you need to specify what type(s) the model binders (IModelBinder implementations) are to be registered for.

This is done by using the Autofac.Integration.Mvc.ModelBinderTypeAttribute, like so:

public class StringBinder : IModelBinder
  public override object BindModel(ControllerContext controllerContext, ModelBindingContext bindingContext)
    // Implementation here

Multiple instances of the ModelBinderTypeAttribute can be added to a class if it is to be registered for multiple types.

Register Web Abstractions

The MVC integration includes an Autofac module that will add HTTP request lifetime scoped registrations for the web abstraction classes. This will allow you to put the web abstraction as a dependency in your class and get the correct value injected at runtime.

The following abstract classes are included:

  • HttpContextBase
  • HttpRequestBase
  • HttpResponseBase
  • HttpServerUtilityBase
  • HttpSessionStateBase
  • HttpApplicationStateBase
  • HttpBrowserCapabilitiesBase
  • HttpFileCollectionBase
  • RequestContext
  • HttpCachePolicyBase
  • VirtualPathProvider
  • UrlHelper

To use these abstractions add the AutofacWebTypesModule to the container using the standard RegisterModule() method.


Enable Property Injection for View Pages

You can make property injection available to your MVC views by adding the ViewRegistrationSource to your ContainerBuilder before building the application container.

builder.RegisterSource(new ViewRegistrationSource());

Your view page must inherit from one of the base classes that MVC supports for creating views. When using the Razor view engine this will be the WebViewPage class.

public abstract class CustomViewPage : WebViewPage
  public IDependency Dependency { get; set; }

The ViewPage, ViewMasterPage and ViewUserControl classes are supported when using the web forms view engine.

public abstract class CustomViewPage : ViewPage
  public IDependency Dependency { get; set; }

Ensure that your actual view page inherits from your custom base class. This can be achieved using the @inherits directive inside your .cshtml file for the Razor view engine:

@inherits Example.Views.Shared.CustomViewPage

When using the web forms view engine you set the Inherits attribute on the @ Page directive inside your .aspx file instead.

<%@ Page Language="C#" MasterPageFile="~/Views/Shared/Site.Master" Inherits="Example.Views.Shared.CustomViewPage"%>

Due to an issue with ASP.NET MVC internals, dependency injection is not available for Razor layout pages. Razor views will work, but layout pages won’t. See issue #349 for more information.

Enable Property Injection for Action Filters

To make use of property injection for your filter attributes call the RegisterFilterProvider() method on the ContainerBuilder before building your container and providing it to the AutofacDependencyResolver.


This allows you to add properties to your filter attributes and any matching dependencies that are registered in the container will be injected into the properties.

For example, the action filter below will have the ILogger instance injected from the container (assuming you register an ILogger. Note that the attribute itself does not need to be registered in the container.

public class CustomActionFilter : ActionFilterAttribute
  public ILogger Logger { get; set; }

  public override void OnActionExecuting(ActionExecutingContext filterContext)

The same simple approach applies to the other filter attribute types such as authorization attributes.

public class CustomAuthorizeAttribute : AuthorizeAttribute
  public ILogger Logger { get; set; }

  protected override bool AuthorizeCore(HttpContextBase httpContext)
    return true;

After applying the attributes to your actions as usual your work is done.

public ActionResult Index()

Enable Injection of Action Parameters

While not common, some folks want to have Autofac populate parameters in action methods when they’re called. It is recommended you use constructor injection on your controller rather than action method injection but you can enable action method injection if you desire:

// The Autofac ExtensibleActionInvoker attempts to resolve parameters
// from the request lifetime scope IF the model binder can't bind
// to the parameter.

Note you can use the InjectActionInvoker() mechanism with your own custom invoker, too.


OWIN Integration

If you are using MVC as part of an OWIN application, you need to:

  • Do all the stuff for standard MVC integration - register controllers, set the dependency resolver, etc.
  • Set up your app with the base Autofac OWIN integration.
  • Add a reference to the Autofac.Mvc5.Owin NuGet package.
  • In your application startup class, register the Autofac MVC middleware after registering the base Autofac middleware.
public class Startup
  public void Configuration(IAppBuilder app)
    var builder = new ContainerBuilder();


    // Register your MVC controllers.

    // Run other optional steps, like registering model binders,
    // web abstractions, etc., then set the dependency resolver
    // to be Autofac.
    var container = builder.Build();
    DependencyResolver.SetResolver(new AutofacDependencyResolver(container));


    // Register the Autofac middleware FIRST, then the Autofac MVC middleware.

Minor gotcha: MVC doesn’t run 100% in the OWIN pipeline. It still needs HttpContext.Current and some other non-OWIN things. At application startup, when MVC registers routes, it instantiates an IControllerFactory that ends up creating two request lifetime scopes. It only happens during app startup at route registration time, not once requests start getting handled, but it’s something to be aware of. This is an artifact of the two pipelines being mangled together. We looked into ways to try working around it but were unable to do so in a clean fashion.

Using “Plugin” Assemblies

If you have controllers in a “plugin assembly” that isn’t referenced by the main application you’ll need to register your controller plugin assembly with the ASP.NET BuildManager.

You can do this through configuration or programmatically.

If you choose configuration, you need to add your plugin assembly to the /configuration/system.web/compilation/assemblies list. If your plugin assembly isn’t in the bin folder, you also need to update the /configuration/runtime/assemblyBinding/probing path.

<?xml version="1.0" encoding="utf-8"?>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          If you put your plugin in a folder that isn't bin, add it to the probing path
      <probing privatePath="bin;bin\plugins" />
        <add assembly="The.Name.Of.Your.Plugin.Assembly.Here" />

If you choose programmatic registration, you need to do it during pre-application-start before the ASP.NET BuildManager kicks in.

Create an initializer class to do the assembly scanning/loading and registration with the BuildManager:

using System.IO;
using System.Reflection;
using System.Web.Compilation;

namespace MyNamespace
  public static class Initializer
    public static void Initialize()
      var pluginFolder = new DirectoryInfo(HostingEnvironment.MapPath("~/plugins"));
      var pluginAssemblies = pluginFolder.GetFiles("*.dll", SearchOption.AllDirectories);
      foreach (var pluginAssemblyFile in pluginAssemblyFiles)
        var asm = Assembly.LoadFrom(pluginAssemblyFile.FullName);

Then be sure to register your pre-application-start code with an assembly attribute:

[assembly: PreApplicationStartMethod(typeof(Initializer), "Initialize")]

Using the Current Autofac DependencyResolver

Once you set the MVC DependencyResolver to an AutofacDependencyResolver, you can use AutofacDependencyResolver.Current as a shortcut to getting the current dependency resolver and casting it to an AutofacDependencyResolver.

Unfortunately, there are some gotchas around the use of AutofacDependencyResolver.Current that can result in things not working quite right. Usually these issues arise by using a product like Glimpse or Castle DynamicProxy that “wrap” or “decorate” the dependency resolver to add functionality. If the current dependency resolver is decorated or otherwise wrapped/proxied, you can’t cast it to AutofacDependencyResolver and there’s no single way to “unwrap it” or get to the actual resolver.

Prior to version 3.3.3 of the Autofac MVC integration, we tracked the current dependency resolver by dynamically adding it to the request lifetime scope. This got us around issues where we couldn’t unwrap the AutofacDependencyResolver from a proxy... but it meant that AutofacDependencyResolver.Current would only work during a request lifetime - you couldn’t use it in background tasks or at application startup.

Starting with version 3.3.3, the logic for locating AutofacDependencyResolver.Current changed to first attempt to cast the current dependency resolver; then to specifically look for signs it was wrapped using Castle DynamicProxy and unwrap it via reflection. Failing that... we can’t find the current AutofacDependencyResolver so we throw an InvalidOperationException with a message like:

The dependency resolver is of type ‘Some.Other.DependencyResolver’ but was expected to be of type ‘Autofac.Integration.Mvc.AutofacDependencyResolver’. It also does not appear to be wrapped using DynamicProxy from the Castle Project. This issue could be the result of a change in the DynamicProxy implementation or the use of a different proxy library to wrap the dependency resolver.

The typical place where this is seen is when using the action filter provider via ContainerBuilder.RegisterFilterProvider(). The filter provider needs to access the Autofac dependency resolver and uses AutofacDependencyResolver.Current to do it.

If you see this, it means you’re decorating the resolver in a way that can’t be unwrapped and functions that rely on AutofacDependencyResolver.Current will fail. The current solution is to not decorate the dependency resolver.

Glimpse Integration

Integration of an MVC application with Glimpse when using Autofac is pretty much the same as with any other integration. However, if you use action method parameter injection (e.g., with builder.InjectActionInvoker()) then Glimpse execution inspection will fail.

You can work around this by adding the following to your Glimpse configuration:

  <glimpse defaultRuntimePolicy="On" endpointBaseUri="~/Glimpse.axd">
        <add type="Glimpse.Mvc.Inspector.ExecutionInspector, Glimpse.Mvc"/>
        <add type="Glimpse.Mvc.Tab.Execution, Glimpse.Mvc"/>

Again, you only need to do this if you’re using the action parameter injection. This is one of the many reasons it’s recommended to use controller constructor injection instead of action method parameter injection.

For more info on why this is (including links to the associated info from Glimpse), check out this issue.

Unit Testing

When unit testing an ASP.NET MVC app that uses Autofac where you have InstancePerRequest components registered, you’ll get an exception when you try to resolve those components because there’s no HTTP request lifetime during a unit test.

The per-request lifetime scope topic outlines strategies for testing and troubleshooting per-request-scope components.


There is an example project showing ASP.NET MVC integration in the Autofac examples repository.