"It can be difficult to maintain a standard look if you must always put the common pieces in place with every web form you build. In ASP.NET 2.0, master pages will make the job easier. Youll only need to write the common pieces once - in the master page. A master page can serve as a template for one or more web forms. Each ASPX web form only needs to define the content unique to itself, and this content will plug into specified areas of the master page layout."
My 2 cents. In Asp.Net 1.1 it has been for quite some time a common practice to do just the same. You just create a class that inherits from System.Web.UI.Page, create some markup and then you can inherit your aspx pages from this class. If we go further to develop some really advanced technique, we can create MasterPage controls (MasterPage and ContentRegion), entirely based on Paul Wilson's excellent demo. Man, if you look at it, it is actually 100% just the same stuff as Asp.Net 2.0 Master Pages. Personally, I don't like the technique of Master Pages. I'm more HttpHandler/HttpModule guy, that likes rendering. I just want pages to be pages.
Friday, July 22, 2005 10:42 PM