Visual Studio makes calling a web service easy, trying to figure out what is going on under the covers is difficult.
How can I see the actual XML generated from my .Net app when making a call to a web service?
Web Services take Web-applications to the Next Level By using Web services, your application can publish its function or message to the rest of the world. Web services use XML to code and to decode data, and SOAP to transport it (using open protocols).
Web services are built on top of open standards such as TCP/IP, HTTP, Java, HTML, and XML. Web services are XML-based information exchange systems that use the Internet for direct application-to-application interaction.
SOAP is an acronym for Simple Object Access Protocol. SOAP is a XML-based protocol for accessing web services. SOAP is a W3C recommendation for communication between applications.
WSDL is an XML notation for describing a web service. A WSDL definition tells a client how to compose a web service request and describes the interface that is provided by the web service provider.
tools like tcptrace or Fiddler can help.
few troubleshooting links:
Tracing WCF with TcpTrace
Using Fiddler and Excel 07 to debug web services
Fiddler Can Make Debugging Easy
MSDN Example code that implements a TraceExtension for SOAP; You can use as-is or modify to log in whatever you want (I used a DB and kept it not only for debugging but to archive all communication for later on).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With