ASP.NET Razor view engine
|Initial release||January 2010|
|Stable release||ASP.NET MVC 4 / 15 August 2012|
|Written in||C#, VB.NET, HTML|
|Operating system||Microsoft Windows|
|Type||Web application framework|
|Website||The Official Microsoft ASP.NET Site|
|Internet media type||
Razor is an ASP.NET programming syntax used to create dynamic web pages with the C# or Visual Basic .NET programming languages. Razor was in development in June 2010 and was released for Microsoft Visual Studio 2010 in January 2011. Razor is a simple-syntax view engine and was released as part of ASP.NET MVC 3 and the Microsoft WebMatrix tool set.
The Razor syntax is a template markup syntax, based on the C# programming language, that enables the programmer to use an HTML construction workflow[clarification needed]. Instead of using the ASP.NET .ASPX markup syntax with
<%= %> symbols to indicate code blocks, Razor syntax starts code blocks with a @ character and does not require explicit closing of the code-block.
Advantages of Razor
The idea behind Razor is to provide an optimized syntax for HTML generation using a code-focused templating approach, with minimal transition between HTML and code. The design reduces the number of characters and keystrokes, and enables a more fluid coding workflow by not requiring explicitly denoted server blocks within the HTML code. Other advantages that have been noted:
- Is not a new language (no major changes to learn)
- Supports IntelliSense (statement completion support)
- Unit Testable
- Supports "layouts" (an alternative to the "master page" concept in classic aspx pages)
Disadvantages Not supported by modern visual editors, like Dreamweaver
- Getting Started with WebMatrix and ASP.NET Web Pages
- ASP.NET Model View Controller
- MVC 3 – Razor View Engine
- Introducing “Razor” – a new view engine for ASP.NET
- ASP.NET, MVC 3, the Razor View Engine and Google Maps
- Bing Maps Application in ASP.NET MVC 4 A Beginners tutorial on using Bing Mapping in ASP.Net, Exploring MVC Features to handle Mobile and desktop views from a single Application - MSDN Article.