ObjectBuilder WorkItem - Just Implement Windsor Features

ObjectBuilder WorkItem - Just Implement Windsor Features

by David Hayden ( Microsoft MVP C# ), Filed: Made Me Smile

 

I gotta huge kick out of this workitem on the ObjectBuilder CodePlex Site this afternoon:

bug: ObjectBuilder isn't as "awesome" as Windsor. Just implement Windsor features.

 

I guess you could take this as an insult, but it really isn't. I look at my dependency injection tool that I have been creating here and there and it is not close to being as cool as Windsor either. In fact, I look to Windsor to figure out what features I need to add to it :)

On a similar note, Michael Puleio seems almost apologetic in his post about breaking changes in the Composite Web Application Block with regard to dependency injection for Pages, User Controls, and Master Pages:

“Note: I know this is now not truly doing by the book dependency injection. However, with the toolset and framework we are building on, it is the best we could do to keep things simple, reliable, and consistent.“

I think this has something to do with the limitations in ObjectBuilder, although you won't hear anyone say that. Maybe limitations isn't an accurate description, but certainly ObjectBuilder would have been better off as a container and not a framework to build containers.

Either way, it is good to see that ObjectBuilder is being modified and I would love to see it become more prevalent in the .NET Developer Community. It certainly has promise and the architecture is really cool - just a bit overarchitected for the need of the community.

 

posted on Friday, October 05, 2007 6:00 PM

Main

News

Green Tea

.NET Development

Enterprise Library

Patterns & Practices