Blog

Why O Why

December 1, 2007

Glenn Block announced on the ALT.NET Yahoo Group that the P&P team is developing a new dependency injection framework. To say it with the words of Captain Alberto Bertorelli from the British sitcom Allo 'Allo:

"What a mistake-a to make-a!"

I mean, there is the wonderful Castle Windsor, the great StructureMap and the magnificent Spring.NET framework. Why is Microsoft reinventing the wheel again? Why is it possible for Scott Gu to provide test project templates for MS Test, NUnit  and MbUnit with the ASP.NET MVC framework and is it not possible for the P&P team to reuse the existing DI containers out there? Why is it possible for a company like Sun to cooperate with and leverage open-source projects and Microsoft seems to fail in this area?

Let's assume for a moment that this new DI container sucks less than ObjectBuilder, but that it can never compete with the existing feature-rich DI containers (seems like a very realistic scenario to me). I can see the discussions coming in my company as to why our team doesn't (want to) use this new shiny DI container from Microsoft as opposed to Castle Windsor and that we should start migrating. What a PITA!

Profile picture of Jan Van Ryswyck

Jan Van Ryswyck

Thank you for visiting my blog. I’m a professional software developer since Y2K. A blogger since Y2K+5. Curator of the Awesome Talks list. Past organizer of the European Virtual ALT.NET meetings. Thinking and learning about all kinds of technologies since forever.

Comments

About

Thank you for visiting my website. I’m a professional software developer since Y2K. A blogger since Y2K+5. Curator of the Awesome Talks list. Past organizer of the European Virtual ALT.NET meetings. Thinking and learning about all kinds of technologies since forever.

Contact information

(+32) 496 38 00 82

infonull@nullprincipal-itnull.be