Geek asks and answers

MVC4 Web API or MVC3 JsonResult

I saw many arguments in favor of why switching from WCF to the web API is a good move, but I have not seen much on porting from the controller with the JsonResult actions to the web API project. Can someone provide the main advantages when switching to the web API platform, or does it make sense not to port and stay on MVC3?

+5
source share
1 answer

WebAPI provides a lot of out of the box stuff that you don’t get with standard JsonResult. For example, the WebAPI is aware of the types of content that the subscriber expects, and can return Json or XML or other types upon request.

, WebAPI - oData, oData HTTP , , - .

WebAPI , - WCF asmx.

JsonResult, .

+8

More articles:


All Articles