I have seen a ton of posts that refer to this MSDN article and I have tried to implement it myself but I am having a problem.  My situation is much like that in the article.  I would like to dynamically alter the Titles and URL for the current and current.parent nodes so that the breadcrumb menu will show meaningful values.  I have added the MSDN articles example code directly into the content page that is responsible for displaying the article a user has chosen and the Titles and URLs do change, once.  When I navigate away from that particular page the breadcrumb always uses my changed values for the new pages current and current.parent nodes.  Since I am going to a new page shouldn't the values for these nodes change and refresh?

 To clarify my sitemap is like this:
<siteMapNode title="Home" url="~/Default.aspx" description="">
    <siteMapNode title="Articles" url="~/ShowCategories.aspx" description="">
        <siteMapNode title="Browse Articles" url="~/BrowseArticles.aspx">
            <siteMapNode title="Article" url="~/ShowArticle.aspx" />
        </siteMapNode>
    </siteMapNode>
</siteMapNode>

When viewing an article I open url: ShowArticle.aspx?ID=123
Breadcrumb reads: Home -> Articles -> Browse Articles -> Article

What I would like to see is: Home -> Articles -> Selected Category -> Selected Article
I can get the above result, but if I were then to click on the Articles link in the breadcrumb to go to the ShowCategories.aspx page, the breadcrumb will now read:
Selected Category -> Selected Article instead of Home -> Articles.

Another option:  I have thought of building the sitemap from a database that contains all of the possible articles, but that would mean I would end up with a sitemap that had thousands of nodes with a URL like ShowArticle.aspx?ID=x.  Also, new articles are added all of the time.  Creating a node for all of these items seems like a bad idea, especially since the MSDN article I reference here was written to address my issue.  Is anyone using this successfully?  Or does anyone have a workaround that does not require a hugely bloated sitemap in memory?

The SiteMapResolve event should really go in global.asax, since it's a global event. I've done this sucessfully on a demo site (see http://www.ipona.com/samples/ANV201%20-%20ASP.NET%202.0%20Navigation.zip) building nodes from news articles. Try moving the code to global.asax; hook up the event in application load and then add in the resolve event as another event procedure.

d

Thanks Dave, that was way more than I had hoped for!