Why does the WebApi controller have to end in the word Controller to work in a web forms environment?Microsoft demo referenced this post
Note: Make sure the name ends in “Controller” and not “Controller1” or similar.
-
Lets assume that I dont want it called XXXController, how do i add a correct route iny in Application_start methodgh9– gh92013-04-15 18:58:41 +00:00Commented Apr 15, 2013 at 18:58
Add a comment
|
1 Answer
Because it is part of Microsoft's strategy (many software companies are following this paradigm) of Convention Over Configuration for their newer technologies.
Wikipedia entry:
Convention over configuration (also known as coding by convention) is a software design paradigm which seeks to decrease the number of decisions that developers need to make, gaining simplicity, but not necessarily losing flexibility. The phrase essentially means a developer only needs to specify unconventional aspects of the application. For example, if there's a class Sale in the model, the corresponding table in the database is called “sales” by default. It is only if one deviates from this convention, such as calling the table “products_sold”, that one needs to write code regarding these names. When the convention implemented by the tool matches the desired behavior, it behaves as expected without having to write configuration files. Only when the desired behavior deviates from the implemented convention is explicit configuration required.
3 Comments
gh9
Lets assume that I dont want it called XXXController, how do i add a correct route iny in my Application_start method
Paul Sasik
@gh9: I don't know, I haven't tried. I would recommend sticking to convention on this however. Trying to force out of COC might give you serious headaches.
Mike Wasson
You can change the convention by replacing the default implementation of IHttpControllerSelector, but that's orthogonal to whether you are using Web Forms. See asp.net/web-api/overview/web-api-routing-and-actions/…