- NHaml (NHaml has been moved from MvcContrib into a separate project)
- Be able to use the same templating / view engine in asp.net MVC.
- Do not have to learn a new templating language if possible.
- Be able to keep the business logic separate from the view templates.
- Have the least learning curve to implement a basic use case.
- Has enough capability to be able to use advance features and capabilities.
- Should be extendable if needed.
- Should have a very strong developer community to support and sort out the bugs with.
- Should be in use for sometime to be able to determine its stability.
In order to render html from our C# REST service we had to look into templating engines available in C#, since we wanted our generated html to be altered on the fly.
We came across the following
4 View engines exist in
In addition we found the following two engines
Asp view from Castle project
Each engine aims to keep the focus on the generated html, and the dynamic contents are inserted into the html.
Our decision about which language to use was based on the following conditions
After doing quite some investigation we decided to go for Spark templating engine, primarily because of the capability of being able to use c# like syntax in templates, and the initial configuration and setup was very simple and easy.