use Fiddler to debug Development Fabric

http://blogs.msdn.com/b/partlycloudy/archive/2009/12/08/configuring-the-storage-client-with-connection-strings.aspx

Development storage connection strings

There are only two options you can specify here. The first is self-explanatory: UseDevelopmentStorage. The only valid value for this is true – if it was false you wouldn’t have used it.

The second option is more interesting. Let’s say you’re running into an error that you don’t quite understand and you can’t get enough information from the debugger to figure out what’s going wrong. You could useFiddler to examine the HTTP requests as they go back and forth to the development storage, but Fiddler doesn’t work when you connect to 12.0.0.1. Enter the second development storage setting:DevelopmentStorageProxyUri! Instead of the regular 127.0.0.1 the host of the Uri you specify in this setting gets used for all accesses to the development storage. Set it to http://ipv4.fiddler and presto – development storage access shows up in Fiddler!

Unfortunately there is an issue with the Fiddler support for blobs and queues returned from listing. Fiddler translates the ipv4.fiddler into 127.0.0.1 before sending the request to the development storage, the absolute Uris returned in response use 127.0.0.1 as the host instead of ipv4.fiddler. Since we don’t modify these Uris when creating objects in the November 2009 version of the storage client, operations performed on them won’t tunnel through Fiddler.

Examples

view sourceprint?

1	"UseDevelopmentStorage=true"

This is the vanilla development storage connection string. Nothing too exciting, but gets the job done.

view sourceprint?

1	"UseDevelopmentStorage=true;DevelopmentStorageProxyUri=http://ipv4.fiddler"

This one is perfect for routing development storage traffic through Fiddler for debugging. Make sure you have Fiddler running before you use this one or it won’t be able to connect!