Re:Introduction to ASP.NET Web API
by darrenkopp on Monday April 02, 2012 @11:21AM
(#3788516)
Yup. Not new at all. MVC has always been able to automatically change it's output based on the Accept header that was passed in on the request. MVC has always been able to be self hosted in something like a console application or windows service so you didn't have to use IIS.
Oh wait, no it doesn't. I guess you could say this is a completely new product that uses a lot of the same patterns as MVC, but ultimately does things very differently.
Re:Introduction to ASP.NET Web API
by euroclydon on Monday April 02, 2012 @11:57AM
(#3788688)
Please show me where this or a previous version of ASP.NET MVC can be hosted in a console app?
Re:Introduction to ASP.NET Web API
by darrenkopp on Monday April 02, 2012 @12:25PM
(#3788834)
It can't. That was sarcasm. My point was that Web API does a lot of things MVC can't.
Re:Introduction to ASP.NET Web API
by euroclydon on Monday April 02, 2012 @01:03PM
(#3789043)
Ok, well the article didn't mention non-IIS hosting either unless I missed it.
Re:Introduction to ASP.NET Web API
by darrenkopp on Tuesday April 03, 2012 @07:13PM
(#3795287)
it's there for Web Api, article may not mention it though.
The process to create a Web API class is identical to the process to create a ASP.NET MVC controller class, that is: - create a class - create public functions - set the route
It's nice make the controller role stand out and have its own name (Web API), however, I feel a bit disappointed if Microsoft touts this as a big feature of the next Visual Studio and .NET Framework.