title: Dependency Injection Container for each Class Library
body: <p>So, this is the first time I'm dealing with DI, please correct me if I misunderstood the whole DI thingy. </p>
  
  <p>These are few of my projects:</p>
  
  <ol>
  <li>Web Application/ Web API Project - Depends on Service Class + inject Automapper (Configuration only applicable for current project)</li>
  <li>Service (Class Library) - Depends on Data Class + inject Automapper (Configuration only applicable for current project)</li>
  <li>Data (Class Library)</li>
  </ol>
  
  <p>My intention was to have each project having its own DI container (says Unity DI). I'm not sure that each project can have its own DI container. </p>
  
  <p>I have read some of the article, showing that it cannot be done (not sure if i interpret them correctly) but I'm not sure why? </p>
  
  <p>If it <strong>cannot</strong> be done, can anyone explain it and how can I achieve this and I doesn't want to register the classes in Data Layer in the Application Layer DI. </p>
  
  <p>If each project <strong>can</strong> have its own DI, when registering the IMapper as instance will it override IMapper of other layers?</p>