This post originated from an RSS feed registered with .NET Buzz by Brendan Tompkins. Original Post: MonoRail --> ASP.NET On Rails? Feed Title: Brendan Tompkins Feed URL: /error.htm?aspxerrorpath=/blogs/brendan.tompkins/Rss.aspx Feed Description: Blog First. Ask Questions Later. Latest .NET Buzz Posts Latest .NET Buzz Posts by Brendan Tompkins Latest Posts From Brendan Tompkins

 

Creating a weblog in 15 minutes

"In 15 minutes, we go from scratch to complete weblog engine: with comments and an administrative interface. But since the actual application only took 58 lines to complete, we also have time left over to do unit testing, examine the logs, and play around with the domain model."

First, go watch that video.  I think you'll be inspired... this is really cool stuff!  After I saw this, I sat there thinking to myself that it would be way cool to see ASP.NET for Rails.  Well, it turns out that there is!  The MonoRail project looks pretty much to me like it's ASP.NET on Rails.

MonoRail (former Castle on Rails) is a MVC web framework inspired on Action Pack. The Action Pack way of development is extremely productive, very intuitive and easily testable.

MonoRail differs from the standard WebForms way of development as it enforces separation of concerns; controllers just handle application flow, models represent the data, and the view is just concerned about presentation logic. Consequently, you write less code and end up with a more maintainable application.

I think we'd all use patterns more if we had  a framework geared towards patterns like Ruby on Rails is for the Model-View-Controller.  Sure, we've got lots of examples of the Provider pattern implemented in the new ASP.NET for things like Membership, which is fine, but how often are we really going to be writing pluggable providers?  I'd bet that more often as ASP.NET developers we'll be writing some sort of CRUD code that is best implemented as MVC.  I've gotta look into this!

-Brendan