Nine ASP.NET Site Navigation Problem Solutions: Part 1
Find out how to use ASP.NET 2.0's site navigation controls to not only make building site navigation displays simple, but also solve real-world problems, such as hiding selected pages, or displaying "breadcrumbs."
by Lee Richardson
July 14, 2006
o far, there's been plenty of ink expended on ASP.NET 2.0's site navigation controls, but most of that coverage lacks details on how to use the new navigation features in the real world. For example, some common real-world questions are: How do you integrate database driven content into your site's navigation? How do you architect your solution to automatically hide pages to which a user lacks permission? What about differentiating the active top level page, or displaying only the children of that active page? Perhaps you need to display navigational elements as images, but aren't sure how to store the filename or image size.
This two-part series explores nine of the most common site map problems and shows how to solve them with ASP.NET 2.0's new navigation features. Part 1 demonstrates how to:
Set up ASP.NET 2.0 site navigation
Display images in navigation
Differentiate active pages
Navigate site map data
Display breadcrumbs (a list of pages between the home page and the current page)
Use custom site map attributes
Construct a site map page
Part two will delve into more advanced site map solutions, such as:
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
o far, there's been plenty of ink expended on ASP.NET 2.0's site navigation controls, but most of that coverage lacks details on how to use the new navigation features in the real world. For example, some common real-world questions are: How do you integrate database driven content into your site's navigation? How do you architect your solution to automatically hide pages to which a user lacks permission? What about differentiating the active top level page, or displaying only the children of that active page? Perhaps you need to display navigational elements as images, but aren't sure how to store the filename or image size.
