Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


Silverlight Cookbook: Switching to another IoC Framework

AddThis Social Bookmark Button
The Rationale As long as I have been using the Dependency Inversion Principle, Microsoft Unity has always been my preferred Inversion-of-Control framework. Consequently, the Silverlight Cookbook has been using Unity 2 in both its domain and query services as well as within the Silverlight client. I never even bothered looking at other frameworks with the exception of NInject, which I used in a Windows Mobile 5 project, and StructureMap, which I learned a lot about while reading Jeremy D. Miller’s posts. Until I read this post where Philip Mateescu compared the performance of the
most popular IoC framework and declared Autofac as the clear winner. Let’s be honest though. I’ve always liked Unity and managed to solve all my IoC and AOP problems with it without too much hassle. However, while analyzing some performance issues in my latest project revealed that its AOP features were not the fastest available. Nevertheless, I would not simply change my strategy based on a single post. In fact, some claim that the comparison was faulty in the first place. But after browsing through the Autofac documentation I really became quite fond of what Autofac does....(Read whole news on source site)

Home : Blog List : Dennis Doomen.NET : Silverlight Cookbook: Switching to another IoC Framework