There are several ways to see the soap traffic. To generate test messages and watch the response, I would consider using soapUI from http://www.soapUI.org. This tool will parse your WSDL and will allow you to build request messages and send them, and it will then record and display the response. It’s also good in that it will allow you to maintain a library of test messages. It has many more features that I’ve never used.
Alternatively, you can use a network monitoring tool like:
- Microsoft’s Network Monitor (https://connect.microsoft.com/site/sitehome.aspx?SiteID=216)
- TcpTrace (see http://www.pocketsoap.com)
- Fiddler (http://www.fiddler2.com/)
- HttpWatch (http://www.httpwatch.com/)
Finally, if you want to make this functionality a permanent part of your code, you can take a look at http://msdn2.microsoft.com/en-us/library/system.web.services.protocols.soapextension.aspx, which includes a very useful example. This code will permit tracing either on the client or the server.
WCF has all of the above beaten, badly. It includes an extensive tracing feature, including complete message tracing, and supplies a program to read the traces. You can even produce traces on both the client and server, and look at them together, as a single session. See the Message Logging and Tracing sections of Administration and Diagnostics.