WebAPI的依赖注入

Question

Scenario:

I created one solution with 2 projects. One is Web API project and another is class library for repositories.

I added ninject as DI into WebAPI project. This blog well defined to use ninject with WebAPI.

I can configure repository Classes in RegisterServices methods in NinjectWebCommon.cs file. This is available in app_start folder of Web api project.

Clarification:

I am confused that, now again i added reference of repository project to web api project to register dependency classes. Then how it is not seperate from repository project.

Questions:

Is this the correct way or i missed anything?

May i misunderstood the concept ? May be reflection to check runtime class find can avoid dependency

Please advise and give any correct blog or sample to explain this

Answer 1

You're missing the 3rd project which is your bridge between your WebAPI and Repository library. Usually it contains your interfaces that your plugin DLL objects would implement and your WebAPI would use. All of your WebAPI code should be using interfaces as it is the job of DI to give you the correct class based on the configuration.

This is what allows you to swap out DLLs, add DLLs for new options, etc. The WebAPI project shouldn't reference the plugin because, well, you made a dependency on something you are trying to make dynamic.