Skip to main content

Layout Nesting in ASP.NET MVC


ASP.NET MVC Layout Nesting

 This article is all about nesting layouts in MVC (master pages for WebForms). Sounds easy and it pretty much is until you come to using sections.
Sections appear to catch people out as they need to be declared in the Layout specified by the content page, so if you have a sub-layout calling a master layout, how do you pass over a scripts section from the content to the master layout. This might catch a couple of people out who consider themselves proficient in MVC. The answer is as simple as nesting the sections too.
It will be good to adhere to the scripts section as many people who deal with layouts will be used to that. Let consider a site that deals with Employee Management. The Employees are of different categories and let’s say we have a controller dedicated to the topic of Employee Department.
If we designed a page for HR department and it layout is completely different from that of Customer Service department and Finance Department.
We decided to use a stylesheet just for HR Department area of the site – no Customer or Finance styles.
What we should always put at the back of our minds when dealing with Nested Layout in ASP.NET MVC is the scripts section has to be nested also so as to have the effects of the scripts in the child layout.

As explained above, if we have HR department page with some menu or different visual effects which is specific to that layout and the general layout of the entire site, we can have all the scripts section defined in the master layout, that is, the jquery and CSS links in the script section of the master layout and nest the script section the HR specific Layout as shown below
  By nesting Layout in a view is to called a master layout within the head section of the child layout as shown below
layout master

In the master layout, we have to provide a script section as shown below
script section

Called the child layout in our view mean to specify the location of the layout in our view as shown below
child layout

In the child layout, we also nest the script section as shown below
nested script

 Complete Master Layout code
master layout code

complete Nested Layout code
nested layout code


Comments

  1. I love the way you explained the concept of layout nesting Engineer. Thank you

    ReplyDelete

Post a Comment

Popular posts from this blog

Classes in C# Explained

C# Class Explained A class is nothing but an encapsulation of properties and methods that are used to represent a real-time entity, as explained by Guru99 . For instance, if you want to work with Guest’s data as in our previous DataDriven Web application . The properties of the Guest would be the Id, GuestName, Address, Phone number etc of the Guest. The methods would include the entry and modification of Guest data. All of these operations can be represented as a class in C# as shown below. using System; namespace CsharpnaijaClassTutorial {     public class Guest     {         public int Id { get ; set ; }         public string GuestName { get ; set ; }         public string Address { get ; set ; }         public string WhomToSee { get ; set ; }     ...

ASP.NET MVC Views

Views in ASP.NET MVC Application explained Find a related article By  Steve Smith  and  Luke Latham from Microsoft Corporation here In the Model-View-Controller (MVC) pattern, the  view  handles the application's data presentation and user interaction. A view is an HTML template with embedded  Razor markup . Razor markup is code that interacts with HTML markup to produce a webpage that's sent to the client. In ASP.NET MVC, views are  .cshtml  files that use the  C# programming language  in Razor markup. Usually, view files are grouped into folders named for each of the application's  controllers . The folders are stored in a  Views  folder at the root of the application as shown: The  Home  controller is represented by a  Home  folder inside the  Views  folder.  The  Home  folder contains the views for the  About ,  Contact , and  Index...

ASP.NET MVC Routing

ASP.NET MVC Routing ASP.NET MVC routing is a pattern matching system that is responsible for mapping incoming browser requests to specified MVC controller actions. When the ASP.NET MVC application launches then the application registers one or more patterns with the framework's route table to tell the routing engine what to do with any requests that matches those patterns. When the routing engine receives a request at runtime, it matches that request's URL against the URL patterns registered with it and gives the response according to a pattern match. Routing pattern is as follows A URL is requested from a browser, the URL is parsed (that is, break into controller and action), the parsed URL is compared to registered route pattern in the framework’s route table, if a route is found, its process and send response to the browser with the required response, otherwise, the HTTP 404 error is send to the browser. Route Properties ASP.NET MVC routes are res...