title: How do the major C# DI/IoC frameworks compare?
body: <p>At the risk of stepping into holy war territory, What are the strengths and weaknesses of these popular DI/IoC frameworks, and could one easily be considered the best? ..:</p>
  
  <ul>
  <li>Ninject</li>
  <li>Unity </li>
  <li>Castle.Windsor</li>
  <li>Autofac</li>
  <li>StructureMap </li>
  </ul>
  
  <p>Are there any other DI/IoC Frameworks for C# that I haven't listed here?</p>
  
  <p>In context of my use case, I'm building a client WPF app, and a WCF/SQL services infrastructure, ease of use (especially in terms of clear and concise syntax), consistent documentation, good community support and performance are all important factors in my choice.</p>
  
  <h2>Update:</h2>
  
  <p>The resources and duplicate questions cited appear to be out of date, can someone with knowledge of all these frameworks come forward and provide some real insight?</p>
  
  <p>I realise that most opinion on this subject is likely to be biased, but I am hoping that someone has taken the time to study all these frameworks and have at least a generally objective comparison.</p>
  
  <p>I am quite willing to make my own investigations if this hasn't been done before, but I assumed this was something at least a few people had done already.</p>
  
  <h2>Second Update:</h2>
  
  <p>If you do have experience with more than one DI/IoC container, please rank and summarise the pros and cons of those, thank you. This isn't an exercise in discovering all the obscure little containers that people have made, I'm looking for comparisons between the popular (and active) frameworks.</p>