This article will show that how can we add multiple master pages in run time and can access their properties.
To achieve this, we need to add one Base master class which will have properties associated to master pages
and we can access properties associated to master pages on content pages im runtime.
'BASE Class:- Make a class inherited from System.Web.UI.Mster.MasterPage which will be placed in App_Code folder.
'BASE MASTER CLASS
Public Class BaseMaster
Inherits System.Web.UI.MasterPage
Private c As String = String.Empty
Public Overridable Property Call() As String
Get
Return "base"
End Get
Set(ByVal value As String)
c = value
End Set
End Property
End Class
In above class we see one property call which declared as virtual property so we can override this property in other master pages inherited to this base master class and can access their properties associated to attached master at runtime.
First Master Page in our application
Below written master page class is using same call property using override as class is inherited from BaseMaster.
'HTML PAGE TAG
<%@ Master Language="VB" AutoEventWireup="true" CodeFile="MasterPage1.master.vb" Inherits="MasterPage1" %>
'CODEBEHIND
Public Class MasterPage1
Inherits BaseMaster
Private c As String = String.Empty
Public Overridable Property Call() As String
Get
Return "OnemoreChild"
End Get
Set(ByVal value As String)
c = value
End Set
End Property
End Class
Second Master Page in our application
Below written master page class is using same call property using override as class is inherited from BaseMaster.
'HTML PAGE TAG
<%@ Master Language="VB" AutoEventWireup="true" CodeFile="MasterPage2.master.vb" Inherits="MasterPage2" %>
'CODEBEHIND
Public Class MasterPage2
Inherits BaseMaster
Private c As String = String.Empty
Public Overridable Property Call() As String
Get
Return "Child"
End Get
Set(ByVal value As String)
c = value
End Set
End Property
End Class
Now below written content page will show that how can we bind different master pages and can access their properties.
One important thing about master page : Runtime check master page and load all attached content pages on init event of page so if we need to bind in runtime so we have to bind on preinit event.
MASTERPAGEFILE property tells that what master page is being used inside content page so we need to change this property in runtime.
'CONTENT PAGE
'HTML TAG
<%@ Page Language="VB" MasterPageFile="~/MasterPage2.master" AutoEventWireup="true" Title="Untitled Page" CodeFile="Default.aspx.vb" Inherits="Default"%>
<%@ MasterType TypeName="BaseMaster" %>
MasterType gives you master class code file from you can access your master page properties and functions.
'CODEBEHIND
Public Class Default
Inherits System.Web.UI.Page
Protected Sub page_preinit(ByVal sender As Object, ByVal e As EventArgs)
If Not (Request.QueryString("Mode") Is Nothing) Then
If Request.QueryString("Mode") = "one" Then
MasterPageFile = "~/MasterPage1.master"
Else
MasterPageFile = "~/MasterPage2.master"
End If
End If
Me.Title = Master.Call
End Sub
End Class
Above code explains that how can we bind master page at runtime and can call property bound to that.
NOTE: THIS ARTICLE IS CONVERTED FROM C# TO VB.NET USING A CONVERSION TOOL. ORIGINAL ARTICLE CAN BE FOUND ON C# CORNER (http://www.c-sharpcorner.com/).