IoC or Dependency Injection frameworks to support for an MVVM framework

Question

I have been developing a new MVVM framework here .

It has some interesting concepts, but I'd like to support multiple IoC containers. Right now I'm supporting just MEF, because it comes with.Net 4.0.

What are some of the more common IoC/DI frameworks I should look into supporting from the start? I'm thinking maybe 3 or so.

Castle Windsor? Ninject?

EDIT:

Just to clarify, I'm asking which IoC/DI frameworks are commonly used today. I was hoping to also learn of some of the new hotness that's out there and I've not heard of yet.

Answer 1

A library or framework should not use a DI Container - only applications should use containers .

Libraries and frameworks should be designed so that they are friendly to any sort of DI , whether or not the user wants to use a container or Poor Man's DI .

Assume that the user will be using Poor Man's DI and you will automatically be container agnostic .

Answer 2

Unity and Castle Windsor should be a must in my opinion, especially Unity since it's used in Prism and it is part of the Enterprise Library (for portability). And Castle windsor for its easy of use (for a broader community)

Answer 3

An alternative would be to provide a simple IoC Container just like Mvvm Light does.