ASP.NET Razor

This is an old revision of this page, as edited by Uzume (talk | contribs) at 13:22, 19 March 2013 (Uzume moved page Microsoft ASP.NET Razor view engine to ASP.NET Razor view engine: Unnecessary developer prefix and naming is more inline with ASP.NET, ASP.NET AJAX, ASP.NET MVC Framework; it is questionable if it even needs ASP.NET...). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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[1] and was released for Microsoft Visual Studio 2010 in January 2011.[2] Razor is a simple-syntax view engine and was released as part of ASP.NET MVC 3 and the Microsoft WebMatrix tool set.[2]

Developer
Developer(s)Microsoft
Initial releaseJanuary 2010
Stable release
ASP.NET MVC 4 / 15 August 2012; 13 years ago (2012-08-15)
Written inC#, VB.NET, HTML
Operating systemMicrosoft Windows
TypeWeb application framework
LicenseProprietary
WebsiteThe Official Microsoft ASP.NET Site
Razor View Engine File Format
Filename extension
.CSHTML, .VBHTML
Internet media type
text/html
Developed byMicrosoft

Introduction

The Razor syntax is a template markup syntax, based on the C# programming language, that enables the programmer to use an HTML construction workflow. 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.[3] 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.[1] Other advantages that have been noted:[4]

  • 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

References