title: Microsoft Dependency Injection Library
body: <p>A would like to make my ASP.NET Core project could see only another library: Api, where I have interfaces. And another library makes wiring for interfaces and their implementation. </p>
  
  <p>Instead of it Microsoft Dependency Injection Library proposes to make a wiring point right in the asp.net project. In this case this project will see both libraries: Api and ApiImpl. And it's not acceptable.</p>
  
  <p>I wanna find a solution like Ninject, for example, does with modules.</p>