WebApi2 Attribute Routing doesn't work unless controller classes are named in a specific manner

Question

I was debugging an issue with attribute routing giving 404s for known-good routes. Well, known-good to me, but they weren't being picked up by the framework. I was grouping my controllers/models into logical units, e.g.:

Auth
    Models
        Model1
        Model2
    Controller

So my "AuthController" is named MyApi.Auth.Controller instead of, for instance, MyApi.Auth.AuthController.

My routes were not being picked up until I renamed my controller, adding anything before it, e.g. zzController. This makes me think there's a bug in attribute routing, or am I missing something?

Side note: tags on the post are way off... – Alexei Levenkov Dec 20 '15 at 04:05 — Alexei Levenkov, Dec 20 '15 at 04:05

score 0 · Answer 1 · answered Dec 20 '15 at 04:07

ASP is convention over configuration. Whether they add features that go away from that or not, always stick to the convention when it comes to Controllers and Views. It'll make maintenance so much easier (plus in the next version of MVC, there is no more ApiController, everything is just a Controller).

WebApi2 Attribute Routing doesn't work unless controller classes are named in a specific manner

1 Answers1