Attribute routing (or rather, direct routing) shouldn't necessarily be tied to attributes. Just like filter providers can be used to get filters from other places, the same should be true for attribute routing.
Also, the default (attribute) implementation should allow plugging in a custom direct route builder, for cases where the standard RouteAttribute is used but a custom interpretation of the route template is desired.
(This work applies to both MVC and Web API.)
Also, the default (attribute) implementation should allow plugging in a custom direct route builder, for cases where the standard RouteAttribute is used but a custom interpretation of the route template is desired.
(This work applies to both MVC and Web API.)