There has been a lot of noise recently about Inversion of Control (IoC) with .Net recently (stop sniggering at the back java guys!)....
I've been using IoC via the Spring.NET framework for over 2 years now - it's a completely different approach to coding and once you get your head around it everything just falls into place and development is a real joy again.
As I mention, Spring.NET is my framework of choice but a recent change in employer has seen me bump up against Castle/Windsor. First impressions are that I like it - it's not as powerful or feature rich as Spring but that's not always a bad thing! The one thing I did miss though was Visual Studio intellisense when editing the configurations - Spring has an online schema that can be associated with a Spring configuration. This got me thinking - if the VS intellisense can be hooked into that easily why not create one for Windsor configuration?
So I did...you can download it from my new google code site here. Remember to "Readme.txt" once you unzip for instructions!
Enjoy!
I've been using IoC via the Spring.NET framework for over 2 years now - it's a completely different approach to coding and once you get your head around it everything just falls into place and development is a real joy again.
As I mention, Spring.NET is my framework of choice but a recent change in employer has seen me bump up against Castle/Windsor. First impressions are that I like it - it's not as powerful or feature rich as Spring but that's not always a bad thing! The one thing I did miss though was Visual Studio intellisense when editing the configurations - Spring has an online schema that can be associated with a Spring configuration. This got me thinking - if the VS intellisense can be hooked into that easily why not create one for Windsor configuration?
So I did...you can download it from my new google code site here. Remember to "Readme.txt" once you unzip for instructions!
Enjoy!
Comments
You can also register the xsd under XML->Schemas in VS (at least in VS2008). Then just import the namespace in the Castle-config.
You can also specify a lifestyle type of "perWebRequest", although it's not documented.
To modify the schema to support this type, I just added another lifestyle enumeration.
I'm in the process of putting the zip onto codeplex - I'll drop another message when I have uploaded the zip...sixgun - hang on!
Sorry for downtime on this!
James