Skip to main content

70-562 Master Pages

New content placeholder control, need one for any place holding content

We never navigate to a master page but to a content page and asp.net knows it should render the master page.

Their exist two default content place holder.
You can select a master page with the checkbox at the time you create a page.aspx. The new page will now have 2 content place holder one  for head and one for body. Note: There can't be any or head tag in a master page

Master pages can specify default content for pages that don't use a specific place holder, you just add a place holder and add content in it, to generate the new place holder on the page you can select the default place holder, right click->add new place holder.

Typically, the whole content of the master page is put in a table, each place holder in their own cell, in design mode you create a table bellow the place holders, adjust cells(merge cells if needed) and the master page content inside the table + place all the place holders inside cells, then you move the whole table inside the div tag of the master page, go in the style property of the table and set the width to 100%

You can nest master pages, so the sub-master page containing a menu references the base master page that contains the header/footer.


So the base master page has content and place holders, the sub-master page has it's content inside the corresponding place holders of the baseMasterPage, and the content page has it's content inside the palceholders corresponding to the menuMasterPage(subMasterPage).

Comments

Popular posts from this blog

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.