Software:MonoRail
| Developer(s) | Castle Project |
|---|---|
| Stable release | 2.1 RC[1]
/ March 17, 2011 |
| Operating system | Cross-platform |
| Type | Application framework |
| License | Apache 2.0 |
| Website | www |
MonoRail (formerly called Castle on Rails), a component of the Castle Project, is an open source web application framework built on top of the ASP.NET platform. Inspired by Ruby on Rails Action Pack,[2] MonoRail differs from standard ASP.NET Web Forms development by enforcing separation of concerns using a model–view–controller (MVC) architecture.[3] The framework is commonly used in conjunction with Castle ActiveRecord, an ORM layer built on NHibernate. In January 2010, version 2.0 of MonoRail was released, however, many projects use the trunk version of the source to take advantage of new features without waiting for official releases.
Although the project's name is MonoRail, it does not have any affiliation with the Mono project.
How it works
The framework maps web requests to an "action", which is a regular .NET method on the controller. The controller is responsible for invoking business services and controlling the application's flow. When it is time to send the web response to the client, the controller sets a view template to be rendered, putting data in a special dictionary object known as the "Property Bag", and delegates the template rendering to a view engine.
The view engine renders the template into the response stream utilizing the data in the property bag given by the controller. At this stage the view cannot access any other layer of the application, isolating the view from the application logic.
View engines
The mainstream view engine used in MonoRail is NVelocity, based on the Apache Velocity library. NVelocity is supplied with simple control blocks such as if statements and foreach loops. The NVelocity view templates are text files with the extension '.vm'.
Other view engines in use:
- Brail, based on the Boo language. Being a .NET language, the Brail view engine has stronger capabilities, as the view programmer can use the Base Class Library methods. However, power comes with its price, as it opens the possibility to do too much in the view, leaving some responsibility for Separation of concerns in the hands of the programmer. The view templates are text files with the extension '.brail'.
- AspView, a view engine that uses C# as its scripting language, and uses a pre-compiled approach, where all the views are pre-compiled to a .NET Assembly prior to deployment. The view templates are text files with the extension '.aspx'.
- WebForms ViewEngine lets you use some of the power of Web Forms in your MonoRail applications. The use of the WebForms view engine is quite sparse, and is only recommended for a migration phase from an existing Web Forms application to a MonoRail application. The view templates are text files with the extension '.aspx'.
- StringTemplate is the most strict view engine in terms of MVC.[4]
- Spark View Engine is a new view engine popular among ASP.NET MVC developers, supports MonoRail as well.
Other view engines
Building other view engines is quite simple and straightforward. Brail, StringTemplate and AspView were all created by independent developers to suit their own needs.
Other view engine are:
References
Further reading
- James Avery, Jim Holmes, Windows developer power tools, O'Reilly Media, 2006, ISBN:0-596-52754-3, pp. 963–972 (18.6 Simplifying Web Development with Castle MonoRail)
- Steven Sanderson, Pro ASP.NET MVC Framework, Apress, 2009, ISBN:1-4302-1007-9, p. 12 (Comparisons with MonoRail)
External links
Resources
Blogs on MonoRail
- Hamilton Verissimo's Blog, the founder of the Castle Project
- Ayende Rahien's Blog (Oren Eini), the creator of the Brail view engine
- Eleutian's Blog
- .net and other musings
- Ken Egozi's Blog, the creator of the AspView ViewEngine
- Adam Esterline's Blog
 |
