ASP.NET MVC basic routing with parameters

Question

I have been trying to learn ASP.NET MVC 3 and things are going well apart from the routing aspect, whatever I try I just can't seem to get them quite right.

I have an ActionLink on the main page:

@Html.ActionLink("Contracts", "List", "Contract", 
                 new { User.Identity.Name, page=1 })

Which is meant to access this method in the ContractController:

public ViewResult List(string user, int page = 1)
{
    //snip
}

My routes are:

 routes.MapRoute(
     null, 
     "Page{page}",
     new { Controller = "Contract", action = "List" }
 );

 routes.MapRoute(
     null,
     "Page{page}",
     new { Controller = "Contract", action = "List", user = "", page = 1 }
 );

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

The link now will return a 404 error as it can't find the action 'List' in the controller 'Home', which obviously means it didn't use either of the first routes.

Everything worked before I tried to add parameters to the ActionLink, so basically, what am I doing wrong?

Thanks very much.

FYI: You do still have a problem because your first and second routes can't be distinguished on incoming requests. All requests (and output links as well) that should be handled by the second one will be done so by the first. — Robert Koritnik
– Robert Koritnik, Commented Aug 4, 2012 at 8:24
Everything seems to work correctly at the moment. I'm not surprised that one of the routes are redundant, I'm still trying to get my head around routing! Would it make a difference if the first two routes were swapped round? — XN16
– XN16, Commented Aug 4, 2012 at 9:36

jim tollan · Accepted Answer · 2012-08-01 20:38:53Z

1

Alex,

You're doing all the other bits absolutely correctly, however the actionlink has a missing parameter, try this for your actionlink:

@Html.ActionLink("Contracts", "List", "Contract", 
             new { User.Identity.Name, page = 1 }, null)

Adding the null as the final param (htmlAttributes) is all that's missing for you in this scenario (there are 9 overloads for Html.ActionLink, so it's VERY easy to miss the correct implementation).

edited Aug 1, 2012 at 20:38

answered Aug 1, 2012 at 20:33

jim tollan

22.5k4 gold badges53 silver badges64 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

XN16 Over a year ago

Thanks very much, that was exactly the problem! I really need to try and understand the routing system, so far the hardest part of my learning!

jim tollan Over a year ago

no worries alex, another of lifes little mysteries solved. hhmmm, now for the bigger one, the meaning of life!! :-)

Collectives™ on Stack Overflow

ASP.NET MVC basic routing with parameters

1 Answer 1

2 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Linked

Related