Skip to main content

70-562 Navigation

Defining the structure of the site, can be done with sitemap, that can be stored in xml file you can build your own, or create navigation controls.
xmlsitemapprovide

sitemapdatasource

default xml file is web.sitemap, or can use other sources

you can create your own from defiving from the SiteMapProvider, StaticSiteMapProvider you would bind a menu or tree view to the sitemap file.
 
There is a difference puting a slash before a relative url implies this slash is the root folder of the application you can use the ~ to the root directory of the application, because the relative would be affected by location of the master page since it's the containter.

Navigation features:


  • create a sitemap file, containes siteMapNode elements, contains real and virtual page
  • sitemap file integrates localization
  • navigation controls, available from toolbox->Navigation siteMapNode attributes, title, url, and desctiption(tooltip)
 SiteMapPath, Menu, TreeVie, comonly put in the masterpage, on the control set the SiteMapProvider property.

SiteMap can mess up layout if you go deep, configure the max level properties, set the staticdisplaylevel property

A big part of styling navigation is to format those controls, there is autoformat property with presets and preview, msdn is a good one.

The menu control have alot of static and dynamic properties, the breadcrumb control, you can tell the menu to fly out horizontal or vertical, change the seperator for each menu; there are templates for the breadcrub control by default menus will never match the style of the website, but can be configured to anything, there is alot of style customization.

Comments

Post a Comment

Popular posts from this blog

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.
Post a Comment
Read more

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.
4 comments
Read more

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.
Post a Comment
Read more