Using DryIOC in an OWIN-based ASP.NET WebAPI doesn't work

Question

I have a simple app which uses an OWIN-Startup class to configure itself. BUT, I'm not able to get it to work! Here is my configuration:

public void Configuration(IAppBuilder appBuilder) {

    var httpConfiguration = new HttpConfiguration();

    httpConfiguration.Routes.MapHttpRoute(
          name: "default_api_versioned_by_areas",
          routeTemplate: "api/{area}/{controller}/{action}/{id}",
          defaults: new { id = RouteParameter.Optional }
      );

    var container = new Container();

    // registering my services. They're all good....

    container.WithWebApi(
        httpConfiguration, new[] {GetType().Assembly});
    container.RegisterWebApiControllers(
        httpConfiguration, new[] { GetType().Assembly });

    appBuilder.UseDryIocWebApi(httpConfiguration)
        .UseDryIocOwinMiddleware(container);

    appBuilder.UseWebApi(httpConfiguration);

    // I can resolve other services:
    var s = container.Resolve<MyOtherService>();

    // but I cannot resolve controllers:
    var c = container.Resolve<ContentController>();
}

As you can see, MyOtherService is resolvable; But not the ContentController. Also, when I request an API, I get this error:

An error occurred when trying to create a controller of type 'ContentController'. Make sure that the controller has a parameterless public constructor.

Googling doesn't help. Can you help me to figure out how to run the app?

UPDATE:

It seems controllers are not-registered at-all. When I try to resolve the ContentController - which has a default ctor with no-dependency - I get this error:

// code:
var c = container.Resolve<ContentController>();

// exception:

An exception of type 'DryIoc.ContainerException' occurred in DryIoc.dll but was not handled in user code

Additional information: Unable to resolve MyProject.Areas.Alpha.Controllers.ContentController

Where CurrentScope: 

  and ResolutionScope: 

  and Found registrations:

  without matching scope DefaultKey.Of(0),{ID=33, ImplType=MyProject.Areas.Alpha.Controllers.ContentController, Reuse=CurrentScopeReuse {Name="WebRequestScopeName", Lifespan=100}}}

  without matching scope DefaultKey.Of(1),{ID=37, ImplType=MyProject.Areas.Alpha.Controllers.ContentController, Reuse=CurrentScopeReuse {Name="WebRequestScopeName", Lifespan=100}}}

That is a standard error response when unable to resolve controller. One of the dependencies of the controller cannot be resolved. Make sure that all the dependencies of the controller can be resolved by the IoC container. — Nkosi, Jan 21 '17 at 15:23
Error from Update says there are two ContentController registrations. Plus you are not resolving in request scope - error says no matching scope. Just for test `var scope = container.OpenScope(Reuse.WebRequestScopeName); scope.Resolve — dadhi, Jan 21 '17 at 16:49
@dadhi there sure were two `ContentController` registrations. Please post your comment as answer. I was calling `appBuilder.UseWebApi(httpConfiguration)` and `appBuilder.UseDryIocWebApi(httpConfiguration)` both. Removing the second one solved the problem — amiry jd, Jan 22 '17 at 06:52

score 1 · Answer 1 · answered Jan 21 '17 at 15:26

1

That is a standard error response in Web API when the framework is unable to resolve controller. One of the dependencies of the controller cannot be resolved.

For example, if ContentController was defined as

public class ContentController : ApiController {

    public ContentController(IOtherService service) { ... }

}

and the DependencyResovler does not know how to resolve IOtherService then the above stated error will be displayed.

Make sure that all the dependencies of the controller are registered and can be resolved by the IoC container.

answered Jan 21 '17 at 15:26

Nkosi

235,767
35
427
472

I tried to resolve `ContentController` which have a default ctor with no-dependency. It seems controllers are not registered at all. – amiry jd Jan 21 '17 at 15:34
@Javad_Amiry, Just for debugging purposes, If you were to manually register the controller and then try to resolve it, check to see it it would work in that scenario. – Nkosi Jan 21 '17 at 15:47

score 1 · Answer 2 · answered Jan 21 '17 at 18:29

To find exact error why controller is not resolved you may pass throwIfUnresolved parameter to WithWebApi method. By default, resolution of controllers fallbacks to WebApi infrastructure and original exception is swallowed.

container = container.WithWeApi(config, assemblies, throwIfUnresolved: type => type.Name.EndsWith("Controller"));

Using DryIOC in an OWIN-based ASP.NET WebAPI doesn't work

2 Answers2