Dependancy Injection and plugin architecture
Simple enough really, I hope.

I have been messing around with **Castle/Windsor** for a while now in MVC3 and have come to understand ow it works, to an extent. I came across a kickup which now has me forced to merge everything into ASP.NET C# webforms. The tasks sucks but I really do have no choice because of third party components I am required to use.

So that aside and seeing how hard it is to implement Castle with Webforms do I need it? Originally my thought process was that if I need to write a plugable interface into my project for components down the line, much like Wordpress, that maybe it might make my life easier? 

I found a software similar to my needs called **Cuyahoga** and they have implemented Castle with a pluggable architecture. Yet looking at it, it just seems to be one big mess. I'm not refering to the programing skills, I'm refering to the hacking needed to get Castle working in WebForms.

Some talk about **Ninject** and that it supports all .NET framework setups, albeit maybe with a little hacking in comparison to Castle.

What would be my best way to go about writing a plugable architecture and do I require DI.

Or maybe you can help me wire up DI, simply, without the mess on a WebForm page. I have merged my project over but I am unsure how to go about "resolving" the WebForm page so it wires up the ISession etc automatically. I have search high and low for this information. Castle's docs are mainly MVC prone.

Thanks for your time,

Anthony
Dependancy Injection and plugin architecture
===

Simple enough really, I hope.

I have been messing around with **Castle/Windsor** for a while now in MVC3 and have come to understand ow it works, to an extent. I came across a kickup which now has me forced to merge everything into ASP.NET C# webforms. The tasks sucks but I really do have no choice because of third party components I am required to use.

So that aside and seeing how hard it is to implement Castle with Webforms do I need it? Originally my thought process was that if I need to write a plugable interface into my project for components down the line, much like Wordpress, that maybe it might make my life easier? 

I found a software similar to my needs called **Cuyahoga** and they have implemented Castle with a pluggable architecture. Yet looking at it, it just seems to be one big mess. I'm not refering to the programing skills, I'm refering to the hacking needed to get Castle working in WebForms.

Some talk about **Ninject** and that it supports all .NET framework setups, albeit maybe with a little hacking in comparison to Castle.

What would be my best way to go about writing a plugable architecture and do I require DI.

Or maybe you can help me wire up DI, simply, without the mess on a WebForm page. I have merged my project over but I am unsure how to go about "resolving" the WebForm page so it wires up the ISession etc automatically. I have search high and low for this information. Castle's docs are mainly MVC prone.

Thanks for your time,

Anthony