from: 

 

Using MVC, I have an html form helper in my view:

using (Html.BeginForm("ActionOne", "ControllerOne")) ...

Using the default route, the output for the action attribute is as expected:

But registrering a new route with seemingly no matches affects the output.

Routing code:

public static void RegisterRoutes(RouteCollection routes) {
            routes.IgnoreRoute("{resource}.axd/{*pathInfo}");         routes.Add("testRoute", new Route("MyUrl", new MvcRouteHandler()));         routes.MapRoute("Default", "{controller}/{action}", new {
     controller = "Home", action = "Index"}); }

Output:

Is this by design or am I mising something fundamental?

 

I have experienced this exact problem. I'm not sure exactly why the System.Web.Mvc.HtmlHelper seems to just use the first non-ignore route in the routetable to generate links etc from but I have found a workaround for the "BeginForm" issue.

If you have named your "Default" route in the Global.asax.cs, for example:

routes.MapRoute("Default", "{controller}/{action}", new {
    controller = "Home", action = "Index" });

 

Then you can use the Html.BeginFormRoute method and call the name of the "Default" MVC route, then name the controller and action specifically, resulting in the correct url:

using (Html.BeginRouteForm("Default", new {
     controller="YourController", action = "YourFormAction" })) {
     }

 

 

 

Hey, that works. Its still notm ideal thouh, as changing routing on a global scale would need you to edit every occurrence of this :( –
	I agree it isn't ideal and may require some work to update all the uses of BeginForm -> BeginRouteForm if being done on an existing webapp, but if you have all your forms set up to use the default route (as specified above) then as long as you keep that route intact any other changes to routing will not affect the forms, so it is a robust solution. –