Take a Lunch Break with Windsor IoC Container (part of the Castle Project)

Digital Blasphemy - Windsor IoC Container in a Lunch Break

"This is the first post in what will (hopefully) be an occasional series on great tools that are found in many agile developers' toolbox.  The goal of this series is to provide a light introduction to a given technology all the way from the ground up to being able to use the tool in some limited fashion...all in the period of about an hour.  That said, this means that we'll likely be light on theory and edge cases of the tool allowing us to focus only on what we need to start using the tool and then showing you where to look when you need deeper answers.

Windsor is the Inversion of Control (IoC) container piece of the Castle Project, the same guys that bring you MonoRail.  In the short, IoC containers act as a holding structure for the components of your application allowing you to easily decouple them from one another.  This gives you the flexibility to refactor as necessary, replace live implementations of objects with mocked ones, and basically do whatever is necessary to get your system running well in the shortest amount of time.  Although we'll be talking about Windsor exclusively, you may want to check out other .Net IoC containers such as Spring.NET or Jeremy Miller's StructureMap.

..."

This is a short, lunch break length, example of using Castle to uncouple your components, to provide a method of switching out implementations as needed.

I've mention in the last that I've thought Windsor and the entire Castle Project looks pretty interesting. And this post just reinforces that...

(via DotNetKicks.com - Windsor IoC Container in a Lunch Break)