Not exactly news this one, as apparently it’s been around since 15/10 but I had call to do some http traffic inspection on the emulator on a couple of occasions recently. Normally I’d turn to my old friend Fiddler but I’d read somewhere that it couldn’t capture the emulator traffic. That was until Fiddler version 220.127.116.11 was released – it’s now possible to monitor the emulator traffic with Fiddler.
There’s some voodoo involved – at least it seemed like voodoo to me – but lo and behold it worked first time.
For full details see Eric’s post Fiddler and the Windows Phone 7 Emulator. For ease, I’ve reproduced the steps to get up and running from Eric’s post below:
Hi, this is very interesting. Is there a way to do this on an actual device running in release mode? The app I am working on calls to a website - while in debug and running the debugger in release mode, I never have a problem. But while running it purely in release mode, it occasionally gets an error that I have been unable to work out yet why, and it would be useful to use a method like this to see what it is doing, as I am convinced its not actually making the call.
Yes, you should be able to get this to work using the technique outlined here: www.fiddler2.com/.../hookup.asp. I connected via Wifi and set the proxy server on that connection to be the IP address of the machine running Fiddler (with a port of 8888) and I can see the network traffic from the device. Hope that helps, Mike.