R – Problems with a custom route in ASP.NET-MVC

asp.net-mvc-routing

I am having problems with Html.ActionLink when I have a route that takes one parameter.
I have the following routers in global.asx:

        routes.MapRoute(
            "Default",                                              // Route name
            "{controller}/{action}/{id}",                           // URL with parameters
            new { controller = "Home", action = "Index", id = "" }  // Parameter defaults
        );
        routes.MapRoute(
            "materias",
            "{controller}/{action}/{id},{titulo_materia}.html",
            new { controller = "materias", action = "Index", id = "", titulo_materia = "" }  
        );

When I use ActionLink passing two parameters, everything works ok.
But when I try to create a link using the first route I end up with something like:

http://meusite.com/controller-name/[parameter],.html

EDIT:

Here is the action link that i`m having problems:

<span class="editar"><%=Html.ActionLink("Editar", "Edit", "Users", new { id = this.Model.login }, null)%></span>

This link is on another page that is used to manage user data.

Best Answer

First you should put your most generic route at the bottom.

Then, how about doing something like :

    routes.MapRoute(
        "materias",
        "{materias}/{action}/{id},{titulo_materia}.html",
        new { controller = "materias", action = "Index", id = "", titulo_materia = "" }  
    );

    routes.MapRoute(
        "Default",                                              // Route name
        "{controller}/{action}/{id}",                           // URL with parameters
        new { controller = "Home", action = "Index", id = "" }  // Parameter defaults
    );

This way , the materias route only works for the materias controller. (not tested)

EDIT: htmm .. try using martin's example with a small addition :

Html.RouteLink("Link Title", new { controller = "Controller", Action= "Action",id = this.Model.login });

Related Solutions

R – Html.ActionLink construct wrong link when a non-mvc route is added

An alternative option would be to add a custom constraint to your WebFormRoute(s). For example, you could create an implementation of IRouteConstraint to match RouteDirection.IncomingRequest, then use it to ensure the route is ignored by Server-Generated routes (such as ActionLink) but still used by client-generated requests. Something like:

public class IncomingOnlyRouteConstraint: IRouteConstraint
{
    public bool Match(HttpContextBase httpContext, Route route, string parameterName, RouteValueDictionary values, RouteDirection routeDirection)
    {
        if (routeDirection == RouteDirection.IncomingRequest)
        {
            return true;
        }
        return false;
    }
}

And then add the constraint to your route:

routes.Add("AspxRoute", new Route("Upload/New", null, 
                            new RouteValueDictionary() { {"WebFormsConstraint", new IncomingOnlyRouteConstraint()} }, 
                            new WebFormRouteHandler<Page>("~/Uploads.aspx")));

Of course you may prefer to add your own style of constraint, this one is quite limiting on the route that implements it, but it's just an example of one way you could resolve the issue.

C# – ASP.NET MVC Url.Action and route name value

When generating URL your best options is to always use the route names because this way you do not get into the subtleties of the algorithm used to select the route that will be used to generate the URL.

My advice if for you not to use Url.Action and instead use Url.RouteUrl which allows you to specify the name of the route that should be used to construct the URL.

By always using route names you also make your code more robust to changes, for example, you can add new routes without having to worry that they might break your existing code for URL generation.

Best Answer

Related Solutions

R – Html.ActionLink construct wrong link when a non-mvc route is added

C# – ASP.NET MVC Url.Action and route name value

Related Topic