See the scenario described here: https://stackoverflow.com/questions/23732793/multiple-path-to-same-razor-view-asp-net-mvc-breadcrum-using-sitemap-provider/23733872#23733872
For which a solution is demonstrated by NightOwl888's demo code from here:
http://www.shiningtreasures.com/post/2013/08/10/mvcsitemapprovider-4-seo-features#canonical-tag (demo code download https://github.com/NightOwl888/MvcSiteMapProvider-SEO-Features-Tutorial/archive/master.zip)
I am having the same problem as asker, in that, with v4.6.6 of MvcSiteMapProvider, the technique described in the referenced post/article does not work, MvcSiteMapProvider can't use the additional route parameter to differentiate the site map node.
e.g. it can't differentiate:
<mvcSiteMapNode title="About" controller="Home" action="About" />
<mvcSiteMapNode title="Another About" controller="Home" action="About" something="1234" />
and always matches the first one regardless of the urls:
http://somesite.com/home/about
http://somesite.com/home/about?something=1234
However, in the referenced sample code, the technique DOES work, but that code is based on v4.0.6. I was able to confirm the different behaviors between versions.
I suspect that the functionality has been broken and this is a bug.
See the scenario described here: https://stackoverflow.com/questions/23732793/multiple-path-to-same-razor-view-asp-net-mvc-breadcrum-using-sitemap-provider/23733872#23733872
For which a solution is demonstrated by NightOwl888's demo code from here:
http://www.shiningtreasures.com/post/2013/08/10/mvcsitemapprovider-4-seo-features#canonical-tag (demo code download https://github.com/NightOwl888/MvcSiteMapProvider-SEO-Features-Tutorial/archive/master.zip)
I am having the same problem as asker, in that, with v4.6.6 of MvcSiteMapProvider, the technique described in the referenced post/article does not work, MvcSiteMapProvider can't use the additional route parameter to differentiate the site map node.
e.g. it can't differentiate:
<mvcSiteMapNode title="About" controller="Home" action="About" />
<mvcSiteMapNode title="Another About" controller="Home" action="About" something="1234" />
and always matches the first one regardless of the urls:
http://somesite.com/home/about
http://somesite.com/home/about?something=1234
However, in the referenced sample code, the technique DOES work, but that code is based on v4.0.6. I was able to confirm the different behaviors between versions.
I suspect that the functionality has been broken and this is a bug.