Conclusion

There are many ways to structure a web page and many ways that could even produce web pages that look identical. Each of these ways is not necessarily equivalent, some of them are better than others.

Master pages in ASP.NET allow you to control layout design and add common controls to all pages in the website.

The ASP.NET master page model allows for an arbitrary number of content placeholders in the master page. Content placeholders include default content. Additional content can be placed in both new and existing ASP.NET pages.

Along with master pages, you can work with themes to provide users with a great user interface. Styles created in CSS can be defined as a theme for an application. We can allow the user to select a style from the given styles and apply them.

When a master contains a reference to another master page, it is called a nested master page. The child master pages can contain some unique properties of their own besides using the layout and other properties of their parent master. All master pages have the extension .master.

A master page can produce different layouts on different browsers like Google Chrome, IE, Mozilla Firefox. This is referred to as browser-specific output. Understanding page lifecycle is very crucial while developing ASP.NET web applications. Most beginners get confused while dealing with concepts like ‘dynamic controls’ and face problems like losing values, states, etc on postbacks. The sequence of events while working with master pages has become more complex. This course sheds some light on these events by explaining the events in their order with importance.