Geek Answers Handbook

WCF service instead of ASMX web service?

I am writing a SOAP server that will act as an endpoint for an external client. An external client expects SOAP 1.1. I will receive embedded business objects in SOAP messages and send them to the internal application, receive responses, and respond with SOAP messages to the eternal client.

A few years ago, I used traditional ASMX-based web services. Now I am exploring WCF services and wondering which approach is best.

1) Should WCF be seen as a superset of ASMX web services?

2) Is there a reason to still write new web services using ASMX instead of WCF?

3) Does WCF provide better opportunities for working with SOAP messages, unlike SOAP extensions?

4) Can I restrict communication with SOAP 1.1 using WCF, how can I change web.config in ASMX?

5) Does WCF have an easy way to register or view requests that get into the service without resorting to something like SOAP extensions?

Sorry, my questions are not very specific; still trying to figure out what i need to know ...

Using VS2008, Windows Server 2008.

Chris

+6
soap visual-studio-2008 web-services wcf asmx
source share
1 answer

I would recommend using WCF. If you configure your WCF service to use basichttpbinding, it will work as a SOAP 1.1 service.

  • WCF replaces several communications technologies, including asmx.
  • I can not come up with any technical reason. You can do this if you have a team that knows asmx but not wcf, or you have a project with many asmx services, and you do not want to introduce new technology.
  • WCF has contract messages , but is not 100% sure what you mean here.
  • Yes basic http binding
  • Yes, you can use WCF tracing
+5
source share

More articles:


All Articles