WebApiConfig中URL式API版本控制：多控制器需重复配置路由吗？有优化方案吗？

Great question! You absolutely don't need to duplicate that route configuration for every single controller—copy-pasting would lead to messy, hard-to-maintain code, especially as you add more versioned controllers or new API versions down the line. There are two clean approaches to solve this:

方案1：自定义路由约束（适配传统路由） #

Instead of locking the route to a single controller, you can create a custom route constraint that matches any controller ending with V1 (or your version suffix). Here's how:

First, create the constraint class to validate controller names:

public class VersionedControllerConstraint : IHttpRouteConstraint
{
    private readonly string _versionSuffix;

    public VersionedControllerConstraint(string versionSuffix)
    {
        _versionSuffix = versionSuffix ?? throw new ArgumentNullException(nameof(versionSuffix));
    }

    public bool Match(HttpRequestMessage request, IHttpRoute route, string parameterName, IDictionary<string, object> values, HttpRouteDirection routeDirection)
    {
        if (values.TryGetValue("controller", out var controllerObj) && controllerObj is string controllerName)
        {
            // Check if the controller name ends with our version suffix (case-insensitive)
            return controllerName.EndsWith(_versionSuffix, StringComparison.OrdinalIgnoreCase);
        }
        return false;
    }
}

Then update your WebApiConfig to use this constraint instead of hardcoding a controller name:

config.Routes.MapHttpRoute(
    name: "Version1",
    routeTemplate: "api/v1/{controller}/{id}",
    defaults: new { id = RouteParameter.Optional },
    constraints: new { controller = new VersionedControllerConstraint("V1") }
);

Now any controller named StudentV1, EmployeeV1, CarV1, etc., will automatically match this route—no more duplicate configs.

方案2：特性路由（更推荐，更灵活） #

If you're open to switching from traditional routing, attribute routing is even cleaner. It lets you define routes directly on your controllers/actions, making the versioning intent explicit and eliminating global route clutter.

For your V1 controllers, just add a [RoutePrefix] attribute at the controller level:

[RoutePrefix("api/v1")]
public class StudentV1Controller : ApiController
{
    // Matches GET api/v1/student/{id}
    [Route("student/{id?}")]
    public IHttpActionResult Get(int? id)
    {
        // Your logic here
        return Ok();
    }
}

[RoutePrefix("api/v1")]
public class EmployeeV1Controller : ApiController
{
    // Matches GET api/v1/employee/{id}
    [Route("employee/{id?}")]
    public IHttpActionResult Get(int? id)
    {
        // Your logic here
        return Ok();
    }
}

You can even make it more dynamic by using the [controller] token to auto-map the controller name (adjusted to remove the V1 suffix if you want cleaner URLs):

[RoutePrefix("api/v1")]
public class StudentV1Controller : ApiController
{
    // Matches GET api/v1/studentv1/{id} (or use regex to strip the V1 if needed)
    [Route("[controller]/{id?}")]
    public IHttpActionResult Get(int? id)
    {
        return Ok();
    }
}

Attribute routing also makes it easier to transition to newer versions later—just change the RoutePrefix to api/v2 for your V2 controllers, and you're done.

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