IoC Not Working In MVC4 by timtas

Hi everyone,

As several folks have discovered, MVC and Web API use two different service resolvers to create their services. We expect that the various service resolver implementations out there (such as Ninject, StructureMap, and many others) will implement the Web API service resolver in addition to the MVC service resolver, so people won't have a problem when they install those packages. Fortunately, the two interfaces have identical APIs, so implementing both is very easy.

The MVC and Web API service resolvers can't be the same because there is no dependency between the two DLLs in which they are defined. We are not planning to add that dependency because would make other scenarios more complicated, such as people who only want to use one framework and not the other.

Thanks,
The ASP.NET Team

Thank you for attaching the project to help us investigate this issue. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.

Hi timtas,

Figured out this problem. MVC and Http don't use the same dependency injector. Sort of a huge pain in the ass, because who uses more than one Dependency Injector in their code. But here is the current class to setup everything for Http.

GlobalConfiguration.Configuration.ServiceResolver.SetResolver(...)

Also same is true for everything else. ModelBinders seem to be some where else too.

I attached a solution that demonstrates the problem. Run the app and make a GET request at:

    http://localhost:55827/api/test/1 (port may vary)

Expected behavior is that my TestController should be instantiated by StructureMapDependencyResolver. Instead the framework is trying to instantiate the controller via parameterless c-tor.

Here is the response I get.

<Exception xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ExceptionType>System.InvalidOperationException</ExceptionType>
<Message>
An error occurred when trying to create a controller of type 'Mvc4IocProblem.Controllers.TestController'. Make sure that the controller has a parameterless public constructor.
</Message>
<StackTrace>
at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpControllerContext controllerContext, Type controllerType)
at System.Web.Http.Dispatcher.DefaultHttpControllerFactory.CreateInstance(HttpControllerContext controllerContext, HttpControllerDescriptor controllerDescriptor)
at System.Web.Http.Dispatcher.DefaultHttpControllerFactory.CreateController(HttpControllerContext controllerContext, String controllerName)
at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsyncInternal(HttpRequestMessage request, CancellationToken cancellationToken)
at System.Web.Http.Dispatcher.HttpControllerDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
</StackTrace>
<InnerException>
<ExceptionType>System.ArgumentException</ExceptionType>
<Message>
Type 'Mvc4IocProblem.Controllers.TestController' does not have a default constructor
</Message>
<StackTrace>
at System.Linq.Expressions.Expression.New(Type type)
at System.Web.Http.Internal.TypeActivator.Create[TBase](Type instanceType)
at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpControllerContext controllerContext, Type controllerType)
</StackTrace>
</InnerException>
</Exception>

Thank you for reporting this issue. Could you please attach a sample project to help us reproduce this issue?

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)