Master Pages, Themes and Navigation Controls

Re: SiteMapResolve event, global.asax and defaultProvider

msalamon — Wed, 24 Oct 2007 15:34:04 GMT

Oops. I have answered my own question. In the Handle() method I was getting the currentNode from the SiteMap object (the default one), not from the custom provider. once I changed that, it worked fine.

Re: SiteMapResolve event, global.asax and defaultProvider

msalamon — Tue, 23 Oct 2007 21:22:18 GMT

Thanks. I now understand what I was doing wrong. However, I am still having some problems, likely in part b/c this is part of sharepoint. My web.config looked like this, with the custom provider set as the default:

I changed my code in global.asax to this:

SiteMapProvider customSiteMapProvider = SiteMap.Providers["CustomProvider"];
customSiteMapProvider.SiteMapResolve += new SiteMapResolveEventHandler(Handle);

It all works fine. but if I change my default provider to CurrentNavSiteMapProvider, then my global.asax throws this exception in the Handle() code:

System.InvalidCastException: Unable to cast object of type 'System.Web.SiteMapNode' to type 'Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode'.

I put some logging code inside my Handle method:

SiteMapNode currentNode = SiteMap.CurrentNode;
HttpContext.Current.Trace.Write("SiteMapProvider = " + currentNode.Provider.Name);

The site map provider that is always listed is the default sitemapprovider, regardless of which sitemapprovider i attached the event handler to.

Just added some more logging and found out something interesting. currentNode.Provider.Name yields the default provider, but e.Provider (from SiteMapResolveEventArgs e) yields the custom provider. Not sure what this means....

Thus, it appears as if the event handling code is still attached to the default (sharepoint) provider. Any ideas?

Thanks

Re: SiteMapResolve event, global.asax and defaultProvider

RichardD — Tue, 23 Oct 2007 18:22:17 GMT

You need to add the event handler to all of the providers, not just the default provider:

foreach (SiteMapProvider provider in SiteMap.Providers)
{
    provider.SiteMapResolve += CustomSiteMapHandler.Handle;
}

SiteMapResolve event, global.asax and defaultProvider

msalamon — Tue, 23 Oct 2007 16:36:37 GMT

I am adding some custom behavior to the display of breadcrumbs. I had read many articles about adding an event handler in the global.axax Application_Start method to do this, as follows:

SiteMap.Provider.SiteMapResolve += new SiteMapResolveEventHandler(CustomSiteMapHandler.Handle);

(I have separately created the CustomSiteMapHandler class, but I could have done this within global.asax.)

I have gotten this to work perfectly, provided that the asp:SiteMapPath tag I am using to render the breadcrumbs references the default sitemap provider. If it references any other provider listed in web.config, however, then the event handling code is skipped entirely.

Can anyone confirm that the event handling only works with the default sitemap provider. If this is not the case, can anyone show me how to have the event handling code work with a non-default provider.