Performance: Fixed issue in SiteMapPathHelper where a passed in start…

…ingNodeKey would cause 2 node searches instead of 1.
maartenba · Feb 12, 2014 · f18befb · f18befb
1 parent c8bebb4
commit f18befb
Showing 1 changed file with 6 additions and 2 deletions.
diff --git a/src/MvcSiteMapProvider/MvcSiteMapProvider/Web/Html/SiteMapPathHelper.cs b/src/MvcSiteMapProvider/MvcSiteMapProvider/Web/Html/SiteMapPathHelper.cs
@@ -127,8 +127,12 @@ public static MvcHtmlString SiteMapPath(this MvcSiteMapHtmlHelper helper, string
         /// <returns>SiteMap path for the current request</returns>
         public static MvcHtmlString SiteMapPath(this MvcSiteMapHtmlHelper helper, string templateName, string startingNodeKey, SourceMetadataDictionary sourceMetadata)
         {
-            ISiteMapNode startingNode = helper.SiteMap.CurrentNode;
-            if (!string.IsNullOrEmpty(startingNodeKey))
+            ISiteMapNode startingNode;
+            if (string.IsNullOrEmpty(startingNodeKey))
+            {
+                startingNode = helper.SiteMap.CurrentNode;
+            }
+            else
             {
                 startingNode = helper.SiteMap.FindSiteMapNodeFromKey(startingNodeKey);
             }