aspnetcore/tutorials/razor-pages/page.md
This tutorial examines the Razor Pages created by scaffolding in the previous tutorial.
:::moniker range=">= aspnetcore-10.0"
Examine the Pages/Movies/Index.cshtml.cs Page Model:
Razor Pages derive from xref:Microsoft.AspNetCore.Mvc.RazorPages.PageModel. By convention, the PageModel derived class is named PageNameModel. For example, the Index page is named IndexModel.
The constructor uses dependency injection to add the RazorPagesMovieContext to the page:
For more information on asynchronous programming with Entity Framework, see Asynchronous code.
When a GET request is made for the page, the OnGetAsync method returns a list of movies to the Razor Page. On a Razor Page, OnGetAsync or OnGet is called to initialize the state of the page. In this case, OnGetAsync gets a list of movies and displays them.
When OnGet returns void or OnGetAsync returns Task, don't use a return statement. For example, examine the Privacy Page:
When the return type is xref:Microsoft.AspNetCore.Mvc.IActionResult or Task<IActionResult>, you must provide a return statement. For example, the Pages/Movies/Create.cshtml.cs OnPostAsync method:
Examine the Pages/Movies/Index.cshtml Razor Page:
Razor can transition from HTML into C# or into Razor-specific markup. When an @ symbol is followed by a Razor reserved keyword, it transitions into Razor-specific markup. Otherwise, it transitions into C#.
The @page Razor directive makes the file an MVC action, which means that it can handle requests. @page must be the first Razor directive on a page. @page and @model are examples of transitioning into Razor-specific markup. For more information, see Razor syntax.
The @model directive specifies the type of the model passed to the Razor Page. In the preceding example, the @model line makes the PageModel derived class available to the Razor Page. The model is used in the @Html.DisplayNameFor and @Html.DisplayFor HTML Helpers on the page.
Examine the lambda expression used in the following HTML Helper:
@Html.DisplayNameFor(model => model.Movie[0].Title)
The xref:Microsoft.AspNetCore.Mvc.Rendering.IHtmlHelper%601.DisplayNameFor%2A HTML Helper inspects the Title property referenced in the lambda expression to determine the display name. The lambda expression is inspected rather than evaluated. That means there's no access violation when model, model.Movie, or model.Movie[0] is null or empty. When the lambda expression is evaluated, for example, by using @Html.DisplayFor(modelItem => item.Title), the model's property values are evaluated.
Select the menu links RazorPagesMovie, Home, and Privacy. Each page shows the same menu layout. The Pages/Shared/_Layout.cshtml file implements the menu layout.
Open and examine the Pages/Shared/_Layout.cshtml file.
Layout templates let you:
Find the @RenderBody() line. RenderBody is a placeholder where all the page-specific views appear, wrapped in the layout page. For example, when you select the Privacy link, the Pages/Privacy.cshtml view renders inside the RenderBody method.
Consider the following markup from the Pages/Movies/Index.cshtml file:
The preceding highlighted markup is an example of Razor transitioning into C#. The { and } characters enclose a block of C# code.
The PageModel base class contains a ViewData dictionary property that you can use to pass data to a view. Add objects to the ViewData dictionary by using a key value pattern. In the preceding sample, the Title property is added to the ViewData dictionary.
The Title property is used in the Pages/Shared/_Layout.cshtml file. The following markup shows the first few lines of the _Layout.cshtml file.
Change the <title> element in the Pages/Shared/_Layout.cshtml file to display Movie rather than RazorPagesMovie.
[!code-cshtml]
Find the following anchor element in the Pages/Shared/_Layout.cshtml file.
<a class="navbar-brand" asp-area="" asp-page="/Index">RazorPagesMovie</a>
Replace the preceding element with the following markup:
<a class="navbar-brand" asp-page="/Movies/Index">RpMovie</a>
The preceding anchor element is a Tag Helper. In this case, it's the Anchor Tag Helper. The asp-page="/Movies/Index" Tag Helper attribute and value creates a link to the /Movies/Index Razor Page. The asp-area attribute value is empty, so the area isn't used in the link. See Areas for more information.
Save the changes and test the app by selecting the RpMovie link. See the _Layout.cshtml file in GitHub if you have any problems.
Test the Home, RpMovie, Create, Edit, and Delete links. Each page sets the title, which you can see in the browser tab. When you bookmark a page, the title is used for the bookmark.
[!NOTE] You may not be able to enter decimal commas in the
Pricefield. To support jQuery validation for non-English locales that use a comma (",") for a decimal point, and non US-English date formats, you must take steps to globalize the app. See this GitHub issue 4076 for instructions on adding decimal comma.
The Layout property is set in the Pages/_ViewStart.cshtml file:
The preceding markup sets the layout file to Pages/Shared/_Layout.cshtml for all Razor files under the Pages folder. See Layout for more information.
Examine the Pages/Movies/Create.cshtml.cs page model:
The OnGet method initializes any state needed for the page. The Create page doesn't have any state to initialize, so Page is returned. Later in the tutorial, an example of OnGet initializing state is shown. The Page method creates a PageResult object that renders the Create.cshtml page.
The Movie property uses the [BindProperty] attribute to opt-in to model binding. When the Create form posts the form values, the ASP.NET Core runtime binds the posted values to the Movie model.
The OnPostAsync method runs when the page posts form data:
If there are any model errors, the form is redisplayed, along with any form data posted. Most model errors are caught on the client before the form is posted. An example of a model error is posting a value for the date field that can't be converted to a date. Client-side validation and model validation are discussed later in the tutorial.
If there are no model errors:
Examine the Pages/Movies/Create.cshtml Razor Page file:
Visual Studio displays the following tags in a distinctive bold font used for Tag Helpers:
<form method="post"><div asp-validation-summary="ModelOnly" class="text-danger"></div><label asp-for="Movie.Title" class="control-label"></label><input asp-for="Movie.Title" class="form-control" /><span asp-validation-for="Movie.Title" class="text-danger"></span>:::image type="content" source="~/tutorials/razor-pages/page/media/tag-helpers-vs2026.png" alt-text="Visual Studio view of Create.cshtml page showing Tag Helper highlighting.":::
The <form method="post"> element is a Form Tag Helper. The Form Tag Helper automatically includes an antiforgery token.
The scaffolding engine creates Razor markup for each field in the model, except the ID, similar to the following code:
The Validation Tag Helpers (<div asp-validation-summary and <span asp-validation-for) display validation errors. Validation is covered in more detail later in this series.
The Label Tag Helper (<label asp-for="Movie.Title" class="control-label"></label>) generates the label caption and [for] attribute for the Title property.
The Input Tag Helper (<input asp-for="Movie.Title" class="form-control">) uses the DataAnnotations attributes and produces HTML attributes needed for jQuery Validation on the client side.
For more information on Tag Helpers such as <form method="post">, see Tag Helpers in ASP.NET Core.
[!div class="step-by-step"] Previous: Add a model Next: Work with a database
:::moniker-end