"ASP. NET 2.0 secrets" Reading Notes (5)

* Masterpage_url: the URL on the template page was mixed up by me last time, so I wrote a method to generate its absolute address, at that time, I still had no idea why ms was designed like this (it would redirect the URL of the Asp.net control to the relative address of the current masterpage, while the HTML URL is redirected to the relative address of the current page ). One of its solutions records: absolute address (this. templatesourcedirectory "+ '/' + URL ),

* Rebasing: Redirection, which is the redirection mentioned above.

* Define template page: in the Web configuration of the current folder, you can set the page in the current folder and the subfolders of the current folder, and this setting is lower than the page setting.

* Title: The title attribute is often set because the head has been identified as runat = "server"

* Stylesheet: It doesn't mean anything. What I want to say is that it can be viewed on page. adding this rule in header is so powerful as to the technical aspects of the topics I know. Similarly, you can add many other attributes to customize a rich and complete page;

* Nullreference: an object of the reference type is empty. Many controls on the webpage are caused by the absence of runat = "server.

* Dynamic loading template page: you can know that the template page can only be loaded in preinit of the page through the lifecycle of the page, this is one of the advantages of adding an intermediate page (that is, between the page class and the current class) to all pages.

* Profile object: add the profile section to the profile section of the system. Web Section in webconfig. You can add one in properies.

* Pagebasetype: set the current base class type in the configuration file. The single file mode is acceptable. Dual files may be faulty with vs template generation and cannot intelligently perceive the configuration file, so it is best to use single file settings.

This chapter ends page179