Specifying master page in Web.config causes every content page to inherit from the master page : Master page « User Control and Master Page « ASP.Net






  1. ASP.Net
  2. User Control and Master Page
  3. Master page

Specifying master page in Web.config causes every content page to inherit from the master page


 
<configuration>
    <system.web>
        <pages masterPageFile="~/Default.master" />
    </system.web>
</configuration>
 

Once specified in this manner, the content page's Page directive can then be : 

<%@ Page Language="VB" %>

You can override the application-wide master page specification by 
declaring a different master page within your content page:

<%@ Page Language="VB" MasterPageFile="~/MyOtherCompany.master" %>








Related examples in the same category

1.Nested master page (C#)
2.Use master page (C#)
3.Master page with trace (C#)
4.Two Master Pages (C#)
5.Link content page with master page
6.Master page with Default Content
7.Master in page derivative
8.Two pieces of contentplaceholder
9.master for print
10.Control title in master page with content page code
11.Nested master page
12.Use image to fill the filler in master page
13.Code behind and master page
14.Specifying the master page for a specific folder in the Web.config file: Use
15.A master page that creates a GUID on the first request (C#)
16.A master page that creates a GUID on the first request (VB)
17.A master page that exposes a custom property (C#)
18.A master page that exposes a custom property (VB)
19.Exposing a server control from a master page as a public property (C#)
20.Exposing a server control from a master page as a public property (VB)
21.Overriding some default content in the content page (C#)
22.Overriding some default content in the content page (VB)
23.Using Page_PreInit to assign the master page programmatically (C#)
24.Using Page_PreInit to assign the master page programmatically (VB)
25.A content page that can work with more than one master page
26.Update the page properties in master page
27.Nested master
28.Put site navigation in the master page
29.Master pages exposing an object model for content pages to programmatically modify elements on the master.