You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug: Patch for #412, fixes one of the issues, which is that when building a HttpContext with the IMvcContextFactory.CreateHttpContext(ISiteMapNode, Uri, TextWriter) overload the query string collection was invalid because it was being passed the ? character from the string which it wasn't expecting.
Bug: Patch for #416, fixes one of the issues, which is a null reference exception in certain (possibly invalid) node configurations. The working theory is this has something to do with an invalid (non-convention based) Area configuration causing the ControllerTypeResolver to return null. See this comment to configure Areas to work with MvcSiteMapProvider properly. Since this failure is due to #392 which was to enable support for MvcCodeRouting and MvcCodeRouting does not support MVC Areas, this proactive solution is being put in place to disable support for MvcCodeRouting when the controllerType is null (indicating it could not be determined), so the null reference exception is not thrown.
