Skip to content

Add option to interpret a result of custom url resolver as MVC url #392

@lvv83

Description

@lvv83

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!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions