Are you talking specifically about the SiteNav/SiteMap stuff? The short
answer is that the Site Nav data store reflects well with an XML-style tree
view of your average Web site and for many applications doesnt change often,
so again lends itself well to XML. Couple that with the fact that for large
dynamic sites you can write an XSLT that auto-generates your site nav source
everytime you publish, its a good store.
There is no reason you cannot write your own SiteMap provider and hook it
up to a datastore other than an XML file. I am pretty sure there are even
samples for how to do just this and also extend the Site nav controls in
ASP.NET 2.0 (or were at one time...I wrote them!).
<da*******@gmai l.com> wrote in message
news:11******** *************@e 56g2000cwe.goog legroups.com...
Hi.
Why is it practical to have the ASP.NET navigation controls based on
XML? I would love to just use databinding and then be able to
dynamically update the navgiation menu (e.g. for a product list).
I tried to use a dropdownlist with hyperlinks for navigation (not the
main navigation -- a navigation subset) and even a listbox, but found
it very cumbersome.
The way I figure it now, is that I have to pull the data over from Sql
Server, convert it to XML, reformat into the appropriate nodes, and the
then populate the navigaiton control..
Is there an easier way to do this? What am I missing??
Thanks in advance!
-Ranginald