New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Microsoft Embraces Dependency Injection in the Framework
Posted by Jonathan Allen on Apr 28, 2008
In order to reduce duplication across frameworks like WCF, WPF, and ASP.NET, Microsoft has formed the Application Framework Core team. The goal of this team is to prevent design issues like the different dependency property systems for WPF and WF.
One of their first projects is the Managed Extensibility Framework or MEF. This project will leverage techniques such as Naming and Activation Services, Dependency Injection, and Duck Typing. Much of the work underlying Microsoft's implementation is based on community feedback. Krzysztof Cwalina writes,
The direct engagement with the DI community is also starting. We gave a talk on the technology at last week’s MVP Summit, and talked with Jeremy Miller (the owner of Structure Map) and Ayende Rahien (Rhino Mocks) . We got lots of great feedback from Jeremy and Ayende and I think their experience in the DI space and their feedback will be invaluable as the project evolves. Thanks guys! We are of course also looking forward to engaging others in the DI community.
While still in the early phases, some early examples of the syntax are available. In .NET tradition, it is based on attributes rather than XML or explicit object passing.
- This article is part of a featured topic series on Agile Techniques
- See more Agile Techniques content at: http://www.infoq.com/agile_techniques
- Other recent content items in this topic
RelatedVendorContent
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Related Sponsor
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
Other Resources
by
Al Tenhundfeld
Posted
MS has used DI for quite a while
by
Jim Leonardo
Posted
ORM, DI, all of this stuff made popular in Java long long ago.
by
serge boulay
Posted
Where is Castle?
by
F Quednau
Posted
Re: Where is Castle?
by
Al Tenhundfeld
Posted
-
If you're interested in this topic, I'd also read the earlier interview on Unity. www.infoq.com/news/2008/04/microsoft-unity
And some popular open source DI frameworks:
Ninject (new but looks very impressive)
ninject.org/
Spring.Net (port of the very successful and established Java framework)
www.springframework.net/
-
MS has used DI as the core for configurability of the Enterprise Library for a long time now, so the real news here is that they're finally making it a focus for a product team rather than just the patterns and practices team. What's good to hear is the engagement with others.
-
A technique that has long existed in the java world and has been the norm for some time now.
-
Should it not at least get honorable mention? www.castleproject.org/container/index.html
In my opinion I still cannot believe the way Microsoft treats extremely popular and successful Open Source Projects. It's all there guys, and we can embrace it NOW. -
Why would you recommend Windsor Castle over Spring.NET? I have heard good things about Castle, but I've not taken the time to sit down and play with it.
Right now, I'm excited about Ninject. If you haven't looked at it, I recommend you do. In my opinion, if you all you want is an intuitive, usable IoC container, Ninject is far better than Spring.NET -- although I believe they're still working on the performance. I'd be very interested to hear your thoughts on Castle v Ninject also.
5 comments
Watch Thread Reply