Microsoft and Dependency Injection
ObjectBuilder seems to implement all the patterns in the world like Builder, Strategy, Factories, Locator to name a few. It is quite a formidable and intimidating opponent to have a duel with and the lack of documentation makes matter worse. So after trying to master it for a couple of weeks, I gave up as there were already lots of other alternatives at my disposal(And Better ones from Open Source Communities, I admit). But with the anouncement of Unity now it seems that Microsoft has admitted the importance of a DI Container in order to build loosely coupled, flexible and testable software components. Still these are early days to state the real usability of the framework but after playing around with it for a few days, I will come up with my own viewpoints on it vis-a-vis other well established open source DI Containers.
One good thing about Ent. Lib. 4.0 is the fact that it is being re-architected to use DI (Read Unity) for all its application blocks which means you are free to use any container of your choice. More importantly we can now hope that Microsoft will come up more softwares in future which support pluggable architecture and a greater degree of flexibility. How this container is going to fare against a myriad of other well known open source DI Containers like Windsor, Spring, StructureMap etc. is still to be seen. But at least we can see a ray of light at the end of a dark tunnel. So hoping for the best while keeping my fingers crossed.
You can download the weekly drop of Unity Framework from here.
