Partial Views
By Steve Smith, Maher JENDOUBI, and Rick Anderson
ASP.NET Core MVC supports partial views, which are useful when you have reusable parts of web pages you want to share between different views.
View or download sample code ((xref:)how to download)
What are Partial Views?
A partial view is a view that is rendered within another view. The HTML output generated by executing the partial view is rendered into the calling (or parent) view. Like views, partial views use the .cshtml file extension.
When Should I Use Partial Views?
Partial views are an effective way of breaking up large views into smaller components. They can reduce duplication of view content and allow view elements to be reused. Common layout elements should be specified in _Layout.cshtml. Non-layout reusable content can be encapsulated into partial views.
If you have a complex page made up of several logical pieces, it can be helpful to work with each piece as its own partial view. Each piece of the page can be viewed in isolation from the rest of the page, and the view for the page itself becomes much simpler since it only contains the overall page structure and calls to render the partial views.
Tip: Follow the Don’t Repeat Yourself Principle in your views.
Declaring Partial Views
Partial views are created like any other view: you create a .cshtml file within the Views folder. There is no semantic difference between a partial view and a regular view - they are just rendered differently. You can have a view that is returned directly from a controller’s ViewResult, and the same view can be used as a partial view. The main difference between how a view and a partial view are rendered is that partial views do not run *_ViewStart.cshtml* (while views do - learn more about *_ViewStart.cshtml* in Layout).
Referencing a Partial View
From within a view page, there are several ways in which you can render a partial view. The simplest is to use Html.Partial, which returns an IHtmlString and can be referenced by prefixing the call with @:
[!code-htmlMain]
1: @using Microsoft.AspNetCore.Mvc.ViewFeatures
2: @{
3: ViewData["Title"] = "About";
4: }
5: <h2>@ViewData["Title"]</h2>
6: <h3>@ViewData["Message"]</h3>
7:
8: @await Html.PartialAsync("AuthorPartial")
9: @Html.Partial("AuthorPartial")
10: @{
11: Html.RenderPartial("AuthorPartial");
12: }
13:
14: @* Render a full view *@
15: @Html.Partial("Contact")
16:
17: @* RenderPartialAsync *@
18: @{
19: await Html.RenderPartialAsync("AuthorPartial");
20: }
The PartialAsync method is available for partial views containing asynchronous code (although code in views is generally discouraged):
[!code-htmlMain]
1: @using Microsoft.AspNetCore.Mvc.ViewFeatures
2: @{
3: ViewData["Title"] = "About";
4: }
5: <h2>@ViewData["Title"]</h2>
6: <h3>@ViewData["Message"]</h3>
7:
8: @await Html.PartialAsync("AuthorPartial")
9: @Html.Partial("AuthorPartial")
10: @{
11: Html.RenderPartial("AuthorPartial");
12: }
13:
14: @* Render a full view *@
15: @Html.Partial("Contact")
16:
17: @* RenderPartialAsync *@
18: @{
19: await Html.RenderPartialAsync("AuthorPartial");
20: }
You can render a partial view with RenderPartial. This method doesn’t return a result; it streams the rendered output directly to the response. Because it doesn’t return a result, it must be called within a Razor code block (you can also call RenderPartialAsync if necessary):
[!code-htmlMain]
1: @using Microsoft.AspNetCore.Mvc.ViewFeatures
2: @{
3: ViewData["Title"] = "About";
4: }
5: <h2>@ViewData["Title"]</h2>
6: <h3>@ViewData["Message"]</h3>
7:
8: @await Html.PartialAsync("AuthorPartial")
9: @Html.Partial("AuthorPartial")
10: @{
11: Html.RenderPartial("AuthorPartial");
12: }
13:
14: @* Render a full view *@
15: @Html.Partial("Contact")
16:
17: @* RenderPartialAsync *@
18: @{
19: await Html.RenderPartialAsync("AuthorPartial");
20: }
Because it streams the result directly, RenderPartial and RenderPartialAsync may perform better in some scenarios. However, in most cases it’s recommended you use Partial and PartialAsync.
[!NOTE] If your views need to execute code, the recommended pattern is to use a view component instead of a partial view.
Partial View Discovery
When referencing a partial view, you can refer to its location in several ways:
// Uses a view in current folder with this name
// If none is found, searches the Shared folder
@Html.Partial("ViewName")
// A view with this name must be in the same folder
@Html.Partial("ViewName.cshtml")
// Locate the view based on the application root
// Paths that start with "/" or "~/" refer to the application root
@Html.Partial("~/Views/Folder/ViewName.cshtml")
@Html.Partial("/Views/Folder/ViewName.cshtml")
// Locate the view using relative paths
@Html.Partial("../Account/LoginPartial.cshtml")You can have different partial views with the same name in different view folders. When referencing the views by name (without file extension), views in each folder will use the partial view in the same folder with them. You can also specify a default partial view to use, placing it in the Shared folder. The shared partial view will be used by any views that don’t have their own version of the partial view. You can have a default partial view (in Shared), which is overridden by a partial view with the same name in the same folder as the parent view.
Partial views can be chained. That is, a partial view can call another partial view (as long as you don’t create a loop). Within each view or partial view, relative paths are always relative to that view, not the root or parent view.
[!NOTE] If you declare a Razor
sectionin a partial view, it will not be visible to its parent(s); it will be limited to the partial view.
Accessing Data From Partial Views
When a partial view is instantiated, it gets a copy of the parent view’s ViewData dictionary. Updates made to the data within the partial view are not persisted to the parent view. ViewData changed in a partial view is lost when the partial view returns.
You can pass an instance of ViewDataDictionary to the partial view:
You can also pass a model into a partial view. This can be the page’s view model, or some portion of it, or a custom object. You can pass a model to Partial,PartialAsync, RenderPartial, or RenderPartialAsync:
You can pass an instance of ViewDataDictionary and a view model to a partial view:
[!code-htmlMain]
1: @using Microsoft.AspNetCore.Mvc.ViewFeatures
2: @using PartialViewsSample.ViewModels
3: @model Article
4:
5: <h2>@Model.Title</h2>
6: @*Pass the authors name to Views\Shared\AuthorPartial.cshtml*@
7: @Html.Partial("AuthorPartial", Model.AuthorName)
8: @Model.PublicationDate
9:
10: @*Loop over the Sections and pass in a section and additional ViewData
11: to the strongly typed Views\Articles\ArticleSection.cshtml partial view.*@
12: @{ var index = 0;
13: @foreach (var section in Model.Sections)
14: {
15: @Html.Partial("ArticleSection", section,
16: new ViewDataDictionary(this.ViewData) { { "index", index } })
17: index++;
18: }
19: }
The markup below shows the Views/Articles/Read.cshtml view which contains two partial views. The second partial view passes in a model and ViewData to the partial view. You can pass new ViewData dictionary while retaining the existing ViewData if you use the constructor overload of the ViewDataDictionary highlighted below:
[!code-htmlMain]
1: @using Microsoft.AspNetCore.Mvc.ViewFeatures
2: @using PartialViewsSample.ViewModels
3: @model Article
4:
5: <h2>@Model.Title</h2>
6: @*Pass the authors name to Views\Shared\AuthorPartial.cshtml*@
7: @Html.Partial("AuthorPartial", Model.AuthorName)
8: @Model.PublicationDate
9:
10: @*Loop over the Sections and pass in a section and additional ViewData
11: to the strongly typed Views\Articles\ArticleSection.cshtml partial view.*@
12: @{ var index = 0;
13: @foreach (var section in Model.Sections)
14: {
15: @Html.Partial("ArticleSection", section,
16: new ViewDataDictionary(this.ViewData) { { "index", index } })
17: index++;
18: }
19: }
Views/Shared/AuthorPartial:
[!code-htmlMain]
1: @model string
2: <div>
3: <h3>@Model</h3>
4: This partial view came from /Views/Shared/AuthorPartial.cshtml.<br />
5: </div>
The ArticleSection partial:
[!code-htmlMain]
1: @using PartialViewsSample.ViewModels
2: @model ArticleSection
3:
4: <h3>@Model.Title Index: @ViewData["index"] </h3>
5: <div>
6: @Model.Content
7: </div>
At runtime, the partials are rendered into the parent view, which itself is rendered within the shared *_Layout.cshtml*
)
| <SITEMAP> <MVC> <ASP> <NET> <DATA> <KIOSK> <FLEX> <SQL> <NOTES> <LINUX> <MONO> <FREEWARE> <DOCS> <ENG> <CHAT ME> <ABOUT ME> < THANKS ME> |