What is razor view engine

The Razor view was introduced with ASP. To understand this concept let us see a small example. In the above line the moment the Razor view sees the tag it is intelligent enough to recognize it as an html tag. After that we are closing the tag i. Listing items. The foreach statement automatically transitions to markup with the open tag. Razor understands the structure of HTML markup, it also transitions automatically back to code when the tag is closed.

The output for the above example is as shown below. Asynchronous actions in MVC 5 What does it mean? Unit testing in.

Filters and Attributes in ASP. Controllers and Actions in MVC apoorva. Brief Journey to Asp. We can see the creation of autom Introduction: These days for checking the Invoice and Payment status, most businesses are busy doing manual progression. Daily, multiple requests are received b We will see creation of a project, building the RPA and TestNG framework. NET , Authentication. As we have created ASP. Net MVC project from an empty project template, so at the moment the application does not contain anything to run.

It will display the Add Scaffold dialog. Select Empty from the Template dropdown and click Add button. Visual Studio will create an Index. Notice that Razor view has a cshtml extension. At the top of this file is a code block that is explicitly setting this Layout property to null.

When you run this application you will see the blank webpage because we have created a View from an Empty template. Let's add some C code to make things more interesting. Previous Page. Next Page. Previous Page Print Page. To access the data within your view data dictionary you can simply perform the same steps as you would with any other view engine - supply the key to the dictionary to retrieve the value as shown below:. This could be anything: a string, a complex type, or any other primitive.

While there is nothing new and exciting to talk about in regards to the view data dictionary, there is a new kid on the block - the ViewBag object. The ViewBag is a dynamic object which can be used to pass data from the controller to the view in the same manner in which you have set it up with the view data dictionary.

Using the Razor view engine, I can pull these values out of the view data dictionary fairly easily with the following syntax. While this works, this same thing can be done a lot cleaner with the ViewBag. To utilize the ViewBag you simply set up the fields in the dynamic ViewBag object. At that point they are available to the rendering view via those same field names. To populate the ViewBag, set it up in the controller action as shown below:.

In the view, access the ViewBag fields directly. This will output the values to the screen as shown below. This is possible because of the ViewBag dynamic type. You also have the option of providing multi-token statements to perform various operations within the view. One such example would be concatenating strings in the view as shown here:. Last but certainly not least is the view model object.

Strongly typing your views is actually quite simple. To set up your view to become strongly typed, include the model declaration at the top of your view as shown here:. As soon as the model type is declared at the top of the view, the view is strongly typed and you can access the members of the view model from the Model keyword as shown on the fifth line in the code above.

Assume that the value of Model. You can also access the model anywhere in the page using the Razor notation as shown here:.

If blocks are created inline within the HTML. A simple if block expression is shown below:. The loop expression in Razor is much more readable and user friendly than its WebForm processor. For example, here is a for loop implementation using the WebForms view engine:. Notice how Razor does not require the explicit closing of Razor notation; it is smart enough to figure out where it starts and when it should stop.

There is something interesting to note about how Razor renders content to the screen. For example, you might have some code that looks like this:. However, there are instances in which you do not want to wrap your markup with another tag. Most constructs that the Razor view engine utilizes are cleaner parallels of the WebForms view engine constructs.

Razor is not a new language, just a different template system for defining your views. While the majority of Razor is quite similar to the WebForms view engine, there is one area which differs quite a bit - the layout system. When using the WebForms view engine, you utilized master pages to define common layout between pages. In Razor, there are no master pages, but rather, layout pages. When you create a new ASP.

In this file you can define the layout that all of your views will use as shown below. The reason for this feature is to remove the redundant page declaration code that you normally see at the top of WebForms applications that defines which master page that view should use.

For example, assume that your site has two modes. Perhaps these two modes are:. Depending upon their current state logged in vs. This file is shown in Listing 2. Towards the bottom, notice the RenderBody method call.

When your view gets rendered to the screen, the contents of that view will be the return value of the RenderBody method. A content section is similar to content tag in the WebForms view engine. You can use content sections in Razor to place content in various places throughout your markup as the sections are defined in the layout file.

This gives the developer the flexibility to create slim and contained views to do exactly what they need to do without the cruft of extraneous content definitions lying around in the view for no reason. A simple example of a view utilizing the footer section is demonstrated below by using the section keyword in Razor.

Since the section is not required, I can also remove the section and the page will also render. Therefore this code will also execute flawlessly. Sections can be placed anywhere in the view. While developing your view you decide to implement all of the sections.

To make the markup and view more readable you can place all of these sections at the bottom of the view as shown below. This is illustrated in Listing 5. Each respective section will be correctly placed into the corresponding location of the HTML resulting in a correctly rendered page as shown in Figure 5.

Razor also introduces an extra nugget of functionality - declarative HTML helpers.