Masterpagefile setting in web.config

[Amit Bansal \(MCT, MCSD.NET\)]

the msdn documentation says that if we can do application level binding by
specifying the masterpagefile attribute in web.config, so that all the pages
in the application are bound to a master page. if we do this, we will not be
able to add any page in the application with server controls outside the
content tags, means all pages have to have the master binding. i made the
setting in web.config. but i can easliy add pages whihc are not binded to
master page file and things are working??????????????

 

[Alan Silver]

the msdn documentation says that if we can do application level binding by
specifying the masterpagefile attribute in web.config, so that all the pages
in the application are bound to a master page. if we do this, we will not be
able to add any page in the application with server controls outside the
content tags, means all pages have to have the master binding. i made the
setting in web.config. but i can easliy add pages whihc are not binded to
master page file and things are working??????????????

A page in the application does not *have* to use the master specified in
the web.config. That setting is a default, to save you adding the
attribute to your Page directive in every page.

Where does MSDN say that every page must use the master set in
web.config?