Problem:
We wanted to use Web.sitemap XML file in ASP.Net to populate our breadcrumb control in our Master Page. The issue with the default functionality of the ASP.Net SiteMapPath tools is that it requires default.aspx to be in the NavigateURL of each link. Functionally that is an acceptable method, but we didn't want to display the default.aspx filename and extension to the user. Removing the filename gives the website cleaner URLs and creates easier links for users and SEO.

Solution:
You have to manipulate the SiteMap object in order to achieve these results. Our project used a Master Page, so in the page load of the master page you need C# code:

protected void Page_Load(object sender, EventArgs e)
    {
        SiteMap.SiteMapResolve += new 
      SiteMapResolveEventHandler(SiteMap_SiteMapResolve);
    }

SiteMapNode SiteMap_SiteMapResolve(object sender, 
SiteMapResolveEventArgs e)
    {        
        SiteMapNode currentNode = SiteMap.CurrentNode.Clone(true);
        SiteMapNode tempNode = currentNode;

        tempNode = _fixParent(tempNode);
        return currentNode;        
    }

protected SiteMapNode _fixParent(SiteMapNode s)
    {        
        s.Url = _normalizeURL(s.Url);

        if (s.ParentNode != null)
        {
           s.ParentNode =  _fixParent(s.ParentNode);
        }
    
        return (s);
    }

protected string _normalizeURL(string s)
    {
        if(s.Contains("default.aspx")) {
            return(s.Substring(0, s.LastIndexOf("/")));
        } else {
            return(s);
        }
    }

This code allows for each page like http://domain.com/category/subcat/ to display the breadcrumb even though it is listed with its complete path and filename (~/category/subcat/default.aspx) in the Web.sitemap file. Looping through the parents fixes link on each breadcrumb to function sans default.aspx as well.

In an aspx page you can't include the runat=”server” attribute for a script file.

Problem:

<script src=”~/scripts/jsfile.js” type=”text/javascript”><script>

Including the runat=”server” attribute will produce a compilation error on the page. A work around to this issue is to use the ResolveUrl() method.

Solution:

<script src=”<%ResolveUrl(”~/scripts/jsfile.js”)%>” type=”text/javascript”></script>

Utilizing the ResolveUrl() method will replace the instance of ~ in the string with the value of the application’s path; thus, providing the same benefit that runat=”server” gives you in style sheet links and image tags.