OK, so you’ve past the point of deciding whether or not you will use an IoC container. Then you find out that is just the beginning of the road. How does that container fit in your application design? Should you pass it around,
In our last drop of MEF, one of the significant changes was the introduction of the ExportProvider. In this next series of posts, we’ll take an in-depth look at what it is, how it’s used by the CompositionContainer, and how you can use it to customize the behavior of the container.
This post is long overdue, but if you hadn’t heard, my bosses Brad Abrams and Krzysztof Cwalina (pronounced Kris-toff Tzvalyna [thanks to Monika Dyrda for the transliteration]) recently completed V2 of the renowned Framework Guidelines book.
What’s New in the 2nd edition?
Updated with new features from .NET Framework 3.0 and 3.5
Tons of new annotations from industry experts
Recently we were fortunate to have Nicholas Blumhardt join the MEF team. Before joining Microsoft, Nick was a busy man building enterprise software solutions, including developing Autofac, one of the popular IoC containers. Nick is very passionate about incorporating software design patterns and principles (S.O.L.I.D.)
Lots of posts on Oxite. I won’t reiterate what they’ve said, though Rob Conery has done a great analysis here. I’ll just share my own quick brutally honest thoughts. There is no excuse for this. There are tons of folks both internal to Microsoft or external that can help people who want to learn good practices for developing software.
Are you building an application that uses MEF? Want to present to the MEF team your app and tell us about your experience?
If so, contact me.