MVC学习六:Razor布局视图之【/Views/Shared/_Layout.cshtml】

本文详细介绍了ASP.NET MVC中布局页面的使用方法,包括如何在子页面中继承布局页面的内容,并通过@section指令定义额外的头部和尾部区域,增强了页面复用性和维护性。

_Layout代码:

 1 <!DOCTYPE html>
 2 <html>
 3 <head>
 4     <meta charset="utf-8" />
 5     <meta name="viewport" content="width=device-width" />
 6     <title>@ViewBag.Title</title>
 7     @RenderSection("headArea", required: false)
 8 </head>
 9 <body>
10     @RenderBody()
11     
12     @RenderSection("bodyArea", required: false)
13     
14 </body>
15 </html>

使用布局页面的子页面代码:

 1 @{
 2     //此页面的  Layout  属性 已经在 _ViewStart.cshtml 里赋值了!
 3     ViewBag.Title = "SonPage";
 4 }
 5 
 6 <!-- 子页面中所有没有使用@section地方都是对应Layout中@RenderBody()-->
 7 <h2>SonPage</h2>
 8 我爱广州小蛮腰~~~~<br />
 9 我爱蹦极~~~10 
11 <!--对应Layout中@RenderSection("bodyArea", required: false) ,required: false不是必填-->
12 @section headArea{
13     我要去跳入 小坑中~~~~~~~~~14     你奈我何?
15               署名:飞龙小朋友
16 }

所有的视图页面都使用了布局页面,因为每次请求都会执行【_ViewStart.cshtml页面】,【_ViewStart.cshtml页面】对页面的Layout属性赋值了。

很多不使用布局页面的都会清空Layout

 1 @{
 2     Layout = null;
 3 }
 4 
 5 <!DOCTYPE html>
 6 
 7 <html>
 8 <head>
 9     <meta name="viewport" content="width=device-width" />
10     <title>TransData</title>
11 </head>
12 <body>
13 </body>
14 </html>

 

转载于:https://www.cnblogs.com/WarBlog/p/7195954.html

引发的异常:“System.InvalidOperationException”(位于 System.Private.CoreLib.dll 中) 引发的异常:“System.InvalidOperationException”(位于 System.Private.CoreLib.dll 中) 引发的异常:“System.InvalidOperationException”(位于 System.Private.CoreLib.dll 中) 引发的异常:“System.InvalidOperationException”(位于 System.Private.CoreLib.dll 中) Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware: Error: An unhandled exception has occurred while executing the request. System.InvalidOperationException: The view 'Index' was not found. The following locations were searched: /Views/PayMain/Index.cshtml /Views/Shared/Index.cshtml at Microsoft.AspNetCore.Mvc.ViewEngines.ViewEngineResult.EnsureSuccessful(IEnumerable`1 originalLocations) at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result) at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|30_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context) 线程 28460 已退出,返回值为 0 (0x0)。
最新发布
08-20
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值