Last post May 02, 2013 05:06 PM by TheNutCracker
May 01, 2013 10:20 AM|TheNutCracker|LINK
I am wanting to learn how to implement Web Services in my ASP.NET applications. I just started reading an article on MSDN that refers to ASP.NET Web Services as "legacy technology". And it goes on to recommend starting any new services projects with WCF.
I have reservations about learning WCF from the get go. I have read that WCF may be a superior technology but it has a much steeper learning curve and lots more overhead to get things done.
So I would like to get some opinions from people who have knowledge of both methods. Sometimes people ask, "What technology should I use?". And the answer often comes back similar to, "The best tool for the job". So, could that be said also of ASP.NET Web
Services versus WCF?
My goal is pretty simple. To be able to get data from a server in the form of JSON data(xml would probably be okay too).
I will probably end up studying both ways unless there is someone who can convince me that learning ASP.NET Web Services(the legacy technology in Microsoft Speak) is a complete waste of time.
May 01, 2013 10:27 AM|Rion Williams|LINK
There are a variety of ways to actually implement Web Services now - however I have worked with WCF in the past and you are correct about the learning curve, but once you pick up on basically how it works and how things are handled it actually isn't all
Microsoft even recommends using WCF as opposed to the older ASP.NET Web Services, so I would probably agree with them that WCF is a much more practical technology to actually take the time to learn (rather than learning something that will soon be obsolete
if it isn't already).
You may also want to take a look into WebAPI, which is the newest member of the .NET Framework family and is geared specifically to simplify web services (in particular RESTful Web Services). The link provided
should give you everything that you need to get started using it as well.
May 01, 2013 03:31 PM|Illeris|LINK
Forget about asmx webservices. They are outdated, and too limited in technology.
WCF is the extended version of webservices. It decouples the service offering from the protocol, and the message encoding. You can consider ASMX webservices as 1 of the options of WCF.
WCF has native JSON support, ASMX does not. It will be much easier to call a webservice using json if the service was a WCF service, then it would be for ASMX services.
May 02, 2013 09:48 AM|sukumarraju|LINK
ASP.NET Web Service (ASMX service) was released as part of Microsoft ASP.NET 2.0 ,
Microsoft has introduced WCF (Windows Communication Foundation) in
.Net 3.0 during 2006 as a unified programming model to implement web service as a replacement to
.Net remoting and ASP.NET Web Services(asmx)
WCF originally targeted SOAP based services where messages are passed in XML format. Even though it is quite feasible to implement
RESTful service using WCF it requires more plumbing/configuration.
WCF is more configuration based rather than convention based.
During August 2012 as part of Visual Studio 2012 and .Net 4.5, MVC 4 release Microsoft introduced
ASP.NET Web API. Web API is light weight framework that allows to implement RESTFul services based on HTTP verbs. It is more convention based rather than configuration based.
ASP.NET Web API has widely adopted due to its simplicity, light weight, HTTP support to implment
RESTFul services. Due to industry's adoption to RESTFul services, demand for SOAP based web services has been drastically disappeared.
Conclusion:- Being said the above WCF is still useful, where as ASP.NET Web API can meet/deliver most of the requirements. Refer below to choose the relevant technology. Get start with Web API
May 02, 2013 05:06 PM|TheNutCracker|LINK
Thank you very much for all the replies I will use all of them for benefit on my quest for infinite wisdom. :)