Using Fiddler 2 to debug your WCF .NET service
A lot of the time I develop .NET services (or clients depending on services) and so far the best debugging tool that I know of is Fiddler (http://www.fiddler2.com/fiddler2/). Do yourself a favour and if you are debugging anything from jQuery asynchronous calls / tricky services / iPhone development / Windows Phone development or even if you want to see what your machine is really sending out to the network around then it’s going to be your saviour. So, now to a simple tip for those that are going to use it to try and figure out what is going on with the WCF service they are developing on their local machine. Here is how to pass all traffic from the service through the Fiddler debugging proxy.
All you need to do is alter your web.config…
|
1 2 3 4 5 6 7 8 9 |
<configuration>
<system.net>
<defaultProxy>
<proxy usesystemdefault="False"
bypassonlocal="True"
proxyaddress="http://127.0.0.1:8888" />
</defaultProxy>
</system.net>
</configuration> |
…and now you will see everything pass through Fiddler. Click on the specific call and start your investigations.
Leave a comment
You must be logged in to post a comment.



