Holy cow, it seems my configuration woes are over!
Ever since I have stumbled upon the Castle project, the Castle.Windsor (I love that name) container has made regular appearances in a lot of my programming projects. Heck, I even built a component based data transportation library to learn how to use it. Unfortunately though, the more we (at our shop) are using it, the more configuration files are appearing all over the place, often with duplicate configuration settings. Seperating things up in include files may get you a little further but often you still wind up with a lot of wordy configuration files.
Luckely though, Ayende Rahien shares our pain and has found a great way to relieve it. Enter Binsor – Boo configuration for Windsor – bringing the fun back to Windsor component configuration!
I downloaded the Rhino.Commons source this weekend, played with Binsor a little and I am very impressed. I was already impressed after seeing the examples on his blog but after experiencing it myself I never want to configure my container with XML again.
Binsor depends on some changes that are not yet in the Castle trunk but you can still use it if you reference the Castle.MicroKernel and Castle.Windsor assemblies packaged with Rhino.Commons.
For your information, Binsor now runs on Windsor’ trunk
Great news Ayende! I try to keep up to date with the source as much as possible but if it wasn’t for your thoughtful reminder I would not have noticed it was available already.
Again, thanks for posting this; I hope you do not mind me feeling somewhat honored by you having found the way to my humble blog.