Shad Storhaug

After contemplating this some more, the logic is definitely wrong for the XML sitemap - it currently excludes the node if any canonical URL or Key is configured. It _should_...

I have confirmed your findings and agree that this is a bug that should be fixed. The Equals and GetHashCode methods need to be overridden in the SiteMapNode to prevent...

> We have, however, implemented a local caching mechanism which caches the WCF results during each request, so the amount of sitemaps or html helpers wouldn't really have any impact....

FYI - The issue you were experiencing with inequality has been fixed in [v4.6.5](https://github.com/maartenba/MvcSiteMapProvider/releases/tag/v4.6.5), but this is still open because there is also a fix coming to prevent the sitemap...

**Using the exact same route values on two different nodes is not supported. This creates ambiguity on which node should selected as the current node.** Ideally, MvcSiteMapProvider should throw an...

Sorry, I didn't mean to sound so harsh. But I put that example in the article to demonstrate why that it is not a good idea to do add multiple...

If I understand you correctly, you are referring to the /sitemap.xml endpoint that generates an XML structure for search engines, correct? Currently, there are no built-in options, but there are...

> A bit of both I think. I was under the impression that the first request after iisreset triggers the generation of the whole sitemap structure in order to show...

FYI - I am working on another project that also has its own sitemap and I did a test with output caching. As it turns out, when writing to a...

I did some experimenting and was able to get MvcSiteMapProvider to work with adequate performance (aside from a delayed initial load) with 15,000 nodes. I am using a 5 year...