tags:

views:

96

answers:

4

Why we are going for WCF when web services (ASMX) exist ??

A: 

Web services require use of HTTP protocol on standard HTTP ports, right? WCF is more flexible. It can be based on HTTP, TCP, UDP and such. It allows you to design an application with network connectivity without caring so much about the protocol used. Then you can more easily switch the network protocol without affecting the application.

BlueMonkMN
+1  A: 
  • WCF supports protocols beyond HTTP (TCP and MSMQ come to mind) and message formats beyond XML, so it could be used for tasks they are unsuitable e.g. because these tasks require better performance.
  • WCF could be self-hosted so no need for hosting in IIS.
  • WCF supports preserving service object state between calls.
elder_george
+2  A: 

Here is a nice article that you can look at

Comparing ASP.NET Web Services to WCF Based on Development

rahul
+1  A: 

Another rather interesting and thoughtful comparison:

http://www.keithelder.net/blog/archive/2008/10/17/WCF-vs-ASMX-WebServices.aspx

Download the PowerPoint and have a look at it - also, watch Keith's DotNetRocks TV appearance for a great screencast intro to WCF and its advantages over ASMX.

Marc

marc_s