The requirement to end the name of your controller with 'Controller' should be relaxed when using attribute routing, since you can unambiguously determine the name of the controller class. The unfortunate side-effect is that all the routes on the incorrectly named controller get silently ignored.
This affects me in Web API, but I expect the limitation is probably also present for MVC controllers with attribute routing.
Comments: We could also consider providing an error if we don't plan to respect the attribute (though this might be interesting to implement because of how controller selection might still get customized).
This affects me in Web API, but I expect the limitation is probably also present for MVC controllers with attribute routing.
Comments: We could also consider providing an error if we don't plan to respect the attribute (though this might be interesting to implement because of how controller selection might still get customized).