I have been using IoC for some time, and I wonder if I will use Microsoft Unity (the official name is "Unity Application Block"). Does anyone have any experience using it? Therefore, since I copied my IoC container code from project to project, but I think it would be better to use something standard. I think IoC can make a huge difference in that component-based applications are loosely coupled and therefore changing, but I am in no way an IoC specialist, so I'm nervous to switch to a framework that would just paint me in the corner as a dependency I will ever want to leave.
I would say that stick to the one you know until you feel confident in this and the whole concept. Then you will have the best solution to choose a structure that completely fills your needs.
I use Unity without real problems. I know that some people like ALT.NET are warning about Unity, but I really think it's just because of the story that the MS P & P team has for writing viruses. Unity has not yet been inflated IMO and works well.
Unity Framework, , " " (, , , , , " ... , , , Unity /).
IoC/Dependency Injection Ninject. , , ( 10 ) .
, .
CompositeWPF ( Prism) - Composite app. Unity , ObjectBuilder. IoC .
Unity
Unity IoC Screencast