Hi,

When you use route hijacking you don't need to set the route. Umbraco handles this for you.

What you are trying to do is called route hijacking : https://our.umbraco.org/documentation/Reference/Templating/Mvc/custom-controllers

Dave

There are occasions where you might want to use custom routing without using route hijacking.

• When you don't actually have nodes to match (virtual node) and you want nice urls. (virtual node), products, news articles etc.
• You might want to reuse a single node for multiple pages.
• You just want to actually have a route so you can use things like Url.Action("ActionResult", "Controller") which really useful when implementing membership and you want to redirect.

In this case you can use UmbracoVirtualNodeRouteHandler

You can use the overload of Umbraco.MapRoute which takes the handler as a parameter to provide a node to return which will populate the RenderModel.

Here's my implementation of one for a virtual logout handler. The LoginRegisterPage class is simply a strong typed model that I convert to internally elsewhere.

/// <summary>
/// The logout virtual node route handler.
/// </summary>
public class LogoutVirtualNodeRouteHandler : UmbracoVirtualNodeRouteHandler
{
    /// <summary>
    /// returns the <see cref="IPublishedContent"/> associated with the route.
    /// </summary>
    /// <param name="requestContext">
    /// The request context.
    /// </param>
    /// <param name="umbracoContext">
    /// The umbraco context.
    /// </param>
    /// <returns>
    /// The <see cref="IPublishedContent"/>.
    /// </returns>
    protected override IPublishedContent FindContent(RequestContext requestContext, UmbracoContext umbracoContext)
    {
        UmbracoHelper helper = new UmbracoHelper(umbracoContext);
        string alias = typeof(LoginRegisterPage).Name;
        return helper.TypedContentAtRoot()
            .First()
            .Descendants()
            .First(d => d.DocumentTypeAlias.InvariantEquals(alias));
    }
}

And the corresponding route.

// Note the use of the "virtual" in the route handler name.
// Logout doesn't exist in the back office.
RouteTable.Routes.MapUmbracoRoute(
  "LogoutPage",
  "Logout/",
  new
  {
    controller = "LoginRegisterPage",
    action = "Logout"
  },
  new LogoutVirtualNodeRouteHandler()); 

Hi James,

Thanks for reply.

i will update my code as above.

Regards

Mehul Gajjar.

is working on a reply...