调整路由优先级使actionMethod生效及路由冲突致参数为空问题咨询

Got it, let's tackle this routing conflict issue you're facing. The core problem here is how ASP.NET matches routes—it uses the order you register them, so if you have two routes with similar template structures, the first one registered will "catch" the request before the second one gets a chance, leading to empty parameters for the latter. Here's how to fix it:

Solution 1: Reorder Your Route Registrations #

You need to register more specific, action-targeted routes before generic ones. Since your email verification and password reset routes both follow the {controller}/{action}/{parameter} pattern, list them in the order you want them to be matched, then finish with the default generic route.

For example:

// First, register your original email verification route
routes.MapRoute(
    name: "EmailVerification",
    url: "{controller}/{action}/{activationCode}",
    defaults: new { controller = "Authentication", action = "VerifyEmail" }
);

// Next, register the password reset route
routes.MapRoute(
    name: "Password",
    url: "{controller}/{action}/{passwordResetCode}",
    defaults: new { controller = "Authentication", action = "ResetPassword" }
);

// Finally, register the default generic route (keep this last!)
routes.MapRoute(
    name: "Default",
    url: "{controller}/{action}/{id}",
    defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
);

Why this works: When a request comes in (like /Authentication/VerifyEmail/XYZ123), ASP.NET checks routes top to bottom. It'll match the first route that fits, so putting your specific authentication routes first ensures they don't get overridden by the default route or each other.

Solution 2: Use Attribute Routing (Cleaner Alternative) #

If you want to avoid managing route order in a central config, switch to attribute routing—it lets you define routes directly on your controller actions, and these take priority over traditional route table routes.

Here's how to set it up:

1. Enable attribute routing in your RouteConfig.cs first:

routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
routes.MapMvcAttributeRoutes(); // Add this line to enable attribute routing

// Keep your default route if needed
routes.MapRoute(
    name: "Default",
    url: "{controller}/{action}/{id}",
    defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
);

2. Add route attributes to your controller actions:

public class AuthenticationController : Controller
{
    [Route("Authentication/VerifyEmail/{activationCode}")]
    public ActionResult VerifyEmail(string activationCode)
    {
        // Your email verification logic here
    }

    [Route("Authentication/ResetPassword/{passwordResetCode}")]
    public ActionResult ResetPassword(string passwordResetCode)
    {
        // Your password reset logic here
    }
}

This approach eliminates route order confusion entirely, since each action has an explicit, unique route that ASP.NET will match directly.

Either solution should fix your parameter-empty issue and let both actions work as expected.

内容的提问来源于stack exchange，提问作者Atefeh Mohammadpoor