What is the difference between DependencyResolver.SetResolver and HttpConfiguration.DependencyResolver in WebAPI

c# asp.net-mvc asp.net-web-api autofac
Jevgenij Nekrasov picture Jevgenij Nekrasov · Mar 19, 2013 · Viewed 30.3k times · Source

I have existing project, which uses AutoFac as IoC.

In the registration code i have these lines:

var resolver = builder.Build();
DependencyResolver.SetResolver(new AutofacDependencyResolver(resolver));
config.DependencyResolver = new AutofacWebApiDependencyResolver(resolver);

So my question is what is the difference between DependencyResolver.SetResolver and HttpConfiguration.DependecyResolver? Why should I assign both of them?

Answer

Steven picture Steven · Mar 19, 2013

Prevent mixing MVC and Web API in the same project. Microsoft seems to suggest this, because the Visual Studio template for Web API mixes the project automatically with MVC, but this is a bad idea.

From an architectural point of view, MVC and Web API are completely different. MVC is a UI technology aimed to optimize end user experience. Web API is a web service technology that is aimed to optimize the experience for the (client) developer.

MVC and Web API don't share any presentation specific code. Mixing them in the same project just makes that project bigger and more complicated.

But perhaps even more importantly, both application types have their own DI configuration needs. They have their own Composition Root and mixing that into a single DI configuration (a single DI container) can make your configuration extraordinary hard.

And last, mixing Web API with MVC in the same project leads to painful ambiguous naming conflicts, since Web API assemblies contains a lot of classes that share the exact same name as MVC counterparts (but with slightly different implementations).

Related questions

How do I resolve Web API controllers using Autofac in a mixed Web API and MVC application?

Hi I have an MVC application where I have defined some dependencies to my Web API. public class AutofacWebApiDependenceResolver : IDependencyResolver { private readonly IComponentContext container; public AutofacWebApiDependenceResolver(IContainer container) { if (container == null) { throw new ArgumentNullException("container"); } this.container = container; } public object …

Read More
Autofac - The request lifetime scope cannot be created because the HttpContext is not available - due to async code?

Short Question: Same as this unanswered problem Long Question: I just ported some code over from an MVC 4 + Web Api solution that was using Autofac into my new solution which is also using Autofac but only with Web Api 2 (no …

Read More
Does autofac supports the new Web Api 2

I'm developing a web api as part of a MVC/API ASP.NET on VS 2013, MVC 5, API 2, but my AutofacWebApiDependencyResolver throws an exception every time I try to register it: Additional information: Inheritance security rules violated while overriding member: 'Autofac.…

Read More