Hello everyone!
I work under integration between MvcSiteMapProvider and MvcCodeRouting projects. This is technically available because your library has very good architecture based on the dependency injection pattern. So, my respects to you! :)
I met one issue, which workaround doesn't seems nice (I got it). The problem is custom url resolver result always treat as non-MVC url (see): node.UsesDefaultUrlResolver() returns false, but I need true, because the node doesn't have url, it is a original SiteMapNode which has passed through specific filter.
Any thoughts? Thanks!
Hello everyone!
I work under integration between MvcSiteMapProvider and MvcCodeRouting projects. This is technically available because your library has very good architecture based on the dependency injection pattern. So, my respects to you! :)
I met one issue, which workaround doesn't seems nice (I got it). The problem is custom url resolver result always treat as non-MVC url (see): node.UsesDefaultUrlResolver() returns false, but I need true, because the node doesn't have url, it is a original SiteMapNode which has passed through specific filter.
Any thoughts? Thanks!