Hi,
Today, I saw that ASP.NET Web API now has [JsonResult](https://aspnetwebstack.codeplex.com/SourceControl/latest#src/System.Web.Http/Results/JsonResult.cs) and even a Json method on ApiController. Just what we needed all along! I cannot think of any words which would describe my reaction when I saw it but maybe this picture can give a hint: [http://i.imgur.com/Bp9an.gif](http://i.imgur.com/Bp9an.gif)
Why on God's green earth do we have this? Why do we try to mess with HTTP and beautiful content negotiation that ASP.NET Web API framework has? This's harm! Please, just remove it and it will be nothing but a commit history.
Thanks!
Comments: @tugberk If I do conneg I almost always do it in the action. It is very rare that I use the same set of media types for all the HTTP methods on a controller, never mind across an entire API. If I want to return JSON I have a JSONContent class that I stuff in a HttpResponseMessage. I have no need for a JSONResult to class to do the same thing.
Today, I saw that ASP.NET Web API now has [JsonResult](https://aspnetwebstack.codeplex.com/SourceControl/latest#src/System.Web.Http/Results/JsonResult.cs) and even a Json method on ApiController. Just what we needed all along! I cannot think of any words which would describe my reaction when I saw it but maybe this picture can give a hint: [http://i.imgur.com/Bp9an.gif](http://i.imgur.com/Bp9an.gif)
Why on God's green earth do we have this? Why do we try to mess with HTTP and beautiful content negotiation that ASP.NET Web API framework has? This's harm! Please, just remove it and it will be nothing but a commit history.
Thanks!
Comments: @tugberk If I do conneg I almost always do it in the action. It is very rare that I use the same set of media types for all the HTTP methods on a controller, never mind across an entire API. If I want to return JSON I have a JSONContent class that I stuff in a HttpResponseMessage. I have no need for a JSONResult to class to do the same thing.