ASP.NET MVC 5属性路由约束：如何适配/promotions/edit/promoId=5格式的URL？

Background #

You're already familiar with using parameter constraints in ASP.NET MVC 5 attribute routing, like this example that restricts promoId to integer values or null:

[Route("edit/{promoId:int?}")]
public ActionResult Edit(int? promoId) { … }

This works for URLs like /promotions/edit/5 or /promotions/edit/, but you want to configure the route to accept URLs in the format /promotions/edit/promoId=5 instead.

Solution #

There are two straightforward approaches to handle this URL format, depending on whether you want a quick implementation or a more reusable, clean solution:

1. Use a Regular Expression Constraint Directly

You can define a regex constraint right in your RouteAttribute to match the promoId=X pattern, then parse the integer value from the captured string in your action method:

// Matches segments that follow exactly "promoId=" + one or more digits
[Route("edit/{promoParam:regex(^promoId=\\d+$)}")]
public ActionResult Edit(string promoParam)
{
    // Extract the integer ID from the parameter string
    if (int.TryParse(promoParam.Split('=')[1], out int promoId))
    {
        // Your business logic here using the parsed promoId
        return View();
    }
    // Return 404 if the format is invalid
    return HttpNotFound();
}

This will only accept URLs like /promotions/edit/promoId=5 (where 5 can be any integer) and reject any other format for that route segment.

2. Create a Custom Route Constraint (Reusable Approach)

For a more maintainable solution, build a custom route constraint that automatically validates the promoId=X format. Here's how:

First, define the constraint class:

public class PromoIdFormatConstraint : IRouteConstraint
{
    public bool Match(HttpContextBase httpContext, Route route, string parameterName, RouteValueDictionary values, RouteDirection routeDirection)
    {
        if (values.TryGetValue(parameterName, out var value) && value is string promoIdStr)
        {
            // Check if the string starts with "promoId=" and the suffix is an integer
            if (promoIdStr.StartsWith("promoId=", StringComparison.OrdinalIgnoreCase))
            {
                return int.TryParse(promoIdStr.Substring("promoId=".Length), out _);
            }
        }
        return false;
    }
}

Next, register the constraint in your RouteConfig.cs so MVC recognizes it:

public class RouteConfig
{
    public static void RegisterRoutes(RouteCollection routes)
    {
        routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

        // Enable attribute routing
        routes.MapMvcAttributeRoutes();

        // Register the custom constraint with a friendly name
        routes.Add("Default", new Route("{controller}/{action}/{id}",
            new RouteValueDictionary(new { controller = "Home", action = "Index", id = UrlParameter.Optional }),
            new RouteValueDictionary(new { promoId = new PromoIdFormatConstraint() })
        ));
    }
}

Finally, use the custom constraint in your RouteAttribute:

[Route("edit/{promoId:PromoIdFormat}")]
public ActionResult Edit(string promoId)
{
    // Parse the integer value once
    int.TryParse(promoId.Substring("promoId=".Length), out int parsedPromoId);
    // Use parsedPromoId in your application logic
    return View();
}

Quick Note: Query String Alternative #

If you actually intended to use a query string format like /promotions/edit?promoId=5 (with a ? separating the path and parameter), you don't need any special route setup. MVC will automatically bind the query string parameter to your action's int? promoId parameter, just like it does with path parameters.

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