The client pointed that the our order wasn’t matching up with what they were seeing internally so I spoke with their developer who suggested that we make sure that the request wasn’t being cached on my machine.

I opened up Fiddler locally and was surprised to see that the none of the request/response data for the connection to the webservice was showing up.

Fiddler, for those that don’t know is a really excellent Http tracing application that allows you to see what kind of http traffic is going in and out over your network connection. You can download fiddler here.

Thankfully, Fiddler runs a simple proxy service which you can point your service requests to in .net using:

if (System.Environment.MachineName.ToLower().Equals("MyMachineName"))
{
    service.Proxy = new System.Net.WebProxy("http://localhost:8888");
}

After adding that code we were off and debugging our .Net service requests in Fiddler!