Ayende has a very interesting post on a new project from Castle called Igloo, a MVC implementation for webforms . Webforms are tricky to adapt to MVC or MVP because of code behind, it makes the view a two part visual and event controller that which in in turn makes the controller a two part controller class and code behind and in turn binds the view to the controller tightly. True degrees of seperation are lost. Igloo does look to make the controller and view not aware nor dependent on each other. If you treat the code behind as a lightweight display mech and allocate more into the controller class then you have a good MVC approach. You will still have the problem of consuming events in the controller class from the view and removing web dependencies in the controller, the many problems of webforms. True MVC on ASP.NET is still the domain of Castle MonoRail but I will explore Igloo will interest. Read More...