title: IoC - Multiple implementations support for a single interface
body: <p>I am wondering why .Net IoC containers do not easily support multiple implementations for a single interface!  May be I am wrong, but as far I have seen, frameworks like Ninject partially supports this feature using annotations (<a href="https://stackoverflow.com/questions/11684022/annotation-based-di-with-producers/11684470#11684470">how?</a>).  I do not think other frameworks like Windsor or simple injector have an easy mechanism to support this scenario.</p>
  
  <p>Is there any reason why this is not supported by many frameworks?  AFAIK, one of the most important reasons to use interfaces is to achieve loose coupling.  If the frameworks designed to improve loose coupling, do not fluently support multiple implementations for a single interface, I do not understand why!</p>
  
  <p>P.S.  Of course I understand that there will be a resolution issue during run time, and the container would be confused which implementation to choose, but that is something which has to be considered in the design, right?</p>