In this Developer Review, we evaluate four view engines available for use with ASP.NET MVC. First, we discuss the role a view engine plays in a website built with ASP.NET MVC, then we provide details about the four view engines in order to help you decide which one suits your needs.
Jason Haley, http://jasonhaley.com/blog/
What Does a View Engine Do?
When we refer to a view engine in ASP.NET MVC, we are talking about three pieces of functionality:
· A template locator/provider (implementation of IViewEngine)
· A template that can render itself (implementation of IView)
· A template engine that can parse and compile the view file syntax into executable code
Combining these three pieces, a view engine provides your controllers with the ability to translate views into Html.
Why Use an Alternate View Engine?
Read more: Greg's Cool [Insert Clever Name] of the Day
Jason Haley, http://jasonhaley.com/blog/
What Does a View Engine Do?
When we refer to a view engine in ASP.NET MVC, we are talking about three pieces of functionality:
· A template locator/provider (implementation of IViewEngine)
· A template that can render itself (implementation of IView)
· A template engine that can parse and compile the view file syntax into executable code
Combining these three pieces, a view engine provides your controllers with the ability to translate views into Html.
Why Use an Alternate View Engine?
Read more: Greg's Cool [Insert Clever Name] of the Day