Henrik Feldt, a competitor in my latest coding challenge, sent me a link to an AVI presentation given by Ayende discussing Castle MonoRail, how it compares to Web Forms development, and the creation of a ground-up application based on this framework. The presentation is a little over an hour long and should greatly shorten the time needed for you to figure out what MonoRail's all about. In the presentation, Ayende does a great job of showing the strengths of MonoRail while not shying away from detailing the up-front work necessary to put it in place.
After using Model View Presenter for 1 1/2 years, and after carefully reviewing other separation-of-concern alternatives, my development team has decided to begin migrating towards Castle MonoRail. With MonoRail, we're hoping to have the fewest number of classes and lowest level of complexity while still supporting test driven development. My biggest concern with moving towards MonoRail was having to abandon third party user controls such as telerik. Although immensely valuable for speeding up development during the early stages of development, I'm finding these types of controls very difficult to alter behaviors later on in a project's life cycle. Another concern, to some, is that MonoRail abandons the ASP.NET page life-cycle. After working within the added complexities of the ASP.NET page life-cycle for seven years, I'm quite excited about getting back to a simpler web model. We'll see how this goes...
Anyway, be sure to check out Ayende's presentation to help make up your own mind.
05-29-2007 11:10 AM