By: Aprendiendo ASP.NET Web API… gratis y en video!! | Jersson on the block!
[...] Web API vs. ASP.NET MVC “APIs” [Ingles][Link] //Muy buen [...]
View ArticleBy: Saeed Neamati
Everything about Web API sounds cool. But I think it’s still in its infancy stage and there are some disadvantages too. For example, I don’t like to use the [FromBody] decorator attribute to make an...
View ArticleBy: Tim G
I am attempting to move my web service from asmx to REST and your article is very helpful, but I am confused a bit because when I try to build a WebAPI application I have to chose ASP.NET MVC 4 Web...
View ArticleBy: Dave Ward
That’s an artifact of how Web API was originally delivered. MVC used to be the only ASP.NET product that shipped out of band, while WebForms updates were bundled with the less frequent .NET framework...
View ArticleBy: Marcel Popescu
One observation: var dfh = js.SerializerSettings.DateFormatHandling; dfh = Newtonsoft.Json.DateFormatHandling.MicrosoftDateFormat; 123 var dfh = js.SerializerSettings.DateFormatHandling; dfh =...
View ArticleBy: Getting SharePoint 2013 apps MVC Apps and ApiControllers to work | Bas...
[…] return views as HTML, whereas the WebAPI is optimized to return structured data. Dave Ward wrote a good post on this subject. When looking at the technical aspects of MVC and WebAPI, there are some...
View ArticleBy: mg1075
I enjoy using Web API, but as an earlier comment by Reuben warned about security issues, I wonder if anyone else finds the prevention of CSRF for ASP.NET Web API as messy as I’m finding it to be.
View ArticleBy: Ruben Bartelink
Thankfully there is good news on the horizon in the form of MVC6 which will stop relying on System.Web and instead live with WebApi and the Razor/ASP.NET WebPages as part of a merged entity (don’t have...
View ArticleBy: mg1075
@Ruben – yes, MVC6 does look like Microsoft trying to go with the “one ASP.NET” approach in a more unified fashion, as opposed to the “one (more) ASP.NET” breakdown alluded to in the humorous linkbait...
View Article
