I promise, this is the last you will see on this subject today (from my part, anyway). It’s for those who were not online yesterday and/or are in a different time zone and/or didn’t see my post from yesterday and/or don’t speak French.
I’ve been working quite a bit with Windows Azure lately and particularly with Table Storage. I used to use SQL Server Mangement Studio to work with SQL Server and I found Azure Storage Explorer (screenshot on the left), which is actually pretty good for working with all three storage options: queues, tables and blobs.
However, I’m a pretty heavy user of LINQPad (which has completely replaced SSMS for me for a while) and, although it’s totally possible to access Azure table storage with “standard LINQPad,” I was missing a few essential features, so I whipped up a LINQPad driver to easily query Azure Table Storage.
What does it do? It allows you to add storage accounts as connections in LINQPad. It supports the local emulator as well as actual cloud storage. With every connection, you get all the right references as well as a typed data context based on the account’s tables.
I think I included everything you can expect from a typed data context, which will work like a charm with auto-completion if you have a LINQPad license. For anything that’s not already there, the data context exposes a
TableClient property that is a CloudTableClient instance. That should be enough to do anything you want.
There’s also a couple of other “bonus” features, such as displaying the requested URL in the “SQL” tab of LINQPad:
If you work with Table Storage and LINQPad (if you haven’t adopted LINQPad yet, it might be the right excuse to test it), don’t hesitate to check the driver out. It would be nice if it got thoroughly tested and if I had feedback.