From here Routing in Asp.net Mvc 4 and Web Api Darin Dimitrov has posted a very good answer which is working for me. It says… You could have a couple of routes: public static class WebApiConfig { public static void Register(HttpConfiguration config) { config.Routes.MapHttpRoute( name: “ApiById”, routeTemplate: “api/{controller}/{id}”, defaults: new { id = RouteParameter.Optional }, … Read more
Attribute routes cannot be inherited. This was a deliberate design decision. We didn’t feel right and didn’t see valid scenarios where it would make sense to inherit them. Could you give a more realistic scenario as to where you would want to use this? [Update(3/24/2014)] In the upcoming 5.2 release of MVC Web API, there … Read more
I was facing the same issue of ‘How to include search parameters as a query string?’, while I was trying to build a web api for my current project. After googling, the following is working fine for me: Api controller action: [HttpGet, Route(“search/{categoryid=categoryid}/{ordercode=ordercode}”)] public Task<IHttpActionResult> GetProducts(string categoryId, string orderCode) { } The url I tried … Read more
By declaring the jsonString parameter with [FromBody] you tell ASP.NET Core to use the input formatter to bind the provided JSON (or XML) to a model. So your test should work, if you provide a simple model class public class MyModel { public string Key {get; set;} } [Route(“Edit/Test”)] [HttpPost] public void Test(int id, [FromBody] … Read more
For an incoming request like /v1/location/1234, as you can imagine it would be difficult for Web API to automatically figure out if the value of the segment corresponding to ‘1234’ is related to appid and not to deviceid. I think you should change your route template to be like [Route(“v1/location/{deviceOrAppid?}”, Name = “AddNewLocation”)] and then … Read more
By default the route configuration follows RESTFul conventions meaning that it will accept only the Get, Post, Put and Delete action names (look at the route in global.asax => by default it doesn’t allow you to specify any action name => it uses the HTTP verb to dispatch). So when you send a GET request … Read more
You can have multiple actions in a single controller. For that you have to do the following two things. First decorate actions with ActionName attribute like [ActionName(“route”)] public class VTRoutingController : ApiController { [ActionName(“route”)] public MyResult PostRoute(MyRequestTemplate routingRequestTemplate) { return null; } [ActionName(“tspRoute”)] public MyResult PostTSPRoute(MyRequestTemplate routingRequestTemplate) { return null; } } Second define the … Read more
The CreatedAtRoute method is intended to return a URI to the newly created resource when you invoke a POST method to store some new object. So if you POST an order item for instance, you might return a route like ‘api/order/11’ (11 being the id of the order obviously). BTW I agree that the MSDN … Read more
I have been scratching my head over this today. My solution is to change the [FromBody] to a HttpRequestMessage, essentially moving up the HTTP stack. In my case I am sending data across the wire which is zipped json which is then base64’d. All this from an android app. The original signature of my web … Read more
Your route map is probably something like this in WebApiConfig.cs: routes.MapHttpRoute( name: “API Default”, routeTemplate: “api/{controller}/{id}”, defaults: new { id = RouteParameter.Optional }); But in order to have multiple actions with the same http method you need to provide webapi with more information via the route like so: routes.MapHttpRoute( name: “API Default”, routeTemplate: “api/{controller}/{action}/{id}”, defaults: … Read more