Before reading this articles you can check ABC of WCF here.
Here are some advantages of WCF in C#.Net:
-It supports HTTP, TCP, Named pipes, MSMQ,P2P bindings.
-It can be hosted in IIS, windows activation service, Self-hosting, Windows service.
-It’s made of a lot of different components, so you can create new components for security, transport, authentication.
-In WCF, there is no need to make much change in code for implementing the security model and changing the binding. Small changes in the configuration will make your requirements.
Here are some advantages of WCF in C#.Net:
-It supports HTTP, TCP, Named pipes, MSMQ,P2P bindings.
-It can be hosted in IIS, windows activation service, Self-hosting, Windows service.
-It’s made of a lot of different components, so you can create new components for security, transport, authentication.
-In WCF, there is no need to make much change in code for implementing the security model and changing the binding. Small changes in the configuration will make your requirements.
-Its faster than ASMX
-Supports Scaling/Load Balancing
-WCF has integrated logging mechanism, changing the configuration file settings will provide this functionality. In other technology developer has to write the code.
-It’s Interoperability, for java, and more.
-WCF is interoperable with other services when compared to .Net Remoting, where the client and service have to be .Net
-WCF services provide better reliability and security in compared to ASMX web services.
-Supports Scaling/Load Balancing
-WCF has integrated logging mechanism, changing the configuration file settings will provide this functionality. In other technology developer has to write the code.
-It’s Interoperability, for java, and more.
-WCF is interoperable with other services when compared to .Net Remoting, where the client and service have to be .Net
-WCF services provide better reliability and security in compared to ASMX web services.
Hello, my name is Bijay. I'm a SharePoint MVP. 