Home/ Questions/Q 7725819
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T05:02:24+00:00

My small Web API project (hosted via SelfHostHttpServer ) has a few dependencies I

  • 0

My small Web API project (hosted via SelfHostHttpServer) has a few dependencies I want to inject into the controllers. In order to do this, I have implemented IDependencyResolver and called httpConfig.ServiceResolver.SetResolver.

This would work fine, except it seems I need to satisfy the internal dependencies the Web API requires. The first time I ran it, I saw that it needed to resolve the controller factory, so I added an instance of DefaultHttpControllerFactory to my container. Now every damn time I refresh the page, it crashes with the next unresolved dependency the framework is trying to resolve.

Am I going about this the wrong way, or am I really supposed to try and guess all of the default implementations and be forced through this crash-fix-refresh cycle of discovering what dependencies are required for the Web API framework to work correctly?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What your resolver is doing in case it can’t resolve the dependency? The proper behaviour should be returning null. ASP.NET Web API DependencyResolver (httpConfig.ServiceResolver) is internally using two resolvers:

    • The one you set through SetResolver (user rosolver)
    • The built in DefaultServiceResolver

    If user resolver returns null for dependency then Web API falls back to DefaultServiceResolver which can handle all built-in dependencies.

    • 0