if we have a master page and a content page.so the content page @Page directive look like as
<%@ Page Language="C#" MasterPageFile="~/Site1.Master" .... />
so , in order to access master page controls in content page we should have to use
<%@ MasterType VirtualPath="~/Site1.Master" %>
so , my question is this why we use @MasterType directive when we already define in the @page directive that this content page is in the master page (here -- Site1.Master)
From Microsoft Docs you are defining the type of the Master property, which allows you to access the properties of your MasterPage derived class.
Provides a way to create a strongly typed reference to the ASP.NET master page when the master page is accessed from the Master property.
As an example:
this.Master.SomePublicPropertyOfMaster = Value;
Specifying the @ MasterType directive with a type of MyMasterPage
results in the following property definition in the code behind class:
public new MyMasterPage Master {
get {
return ({MyMasterPage})base.Master;
}
}
This property definition is created by the BuildMiscClassMembers method of the TemplateControlCodeDomTreeGenerator
class.
来源:https://stackoverflow.com/questions/8946742/why-we-use-master-type