Our organization had prior to the release of the REST API made fairly extensive use of the SOAP API. Unfortunately (I mean fortunately) those have continued working great so I have not had an opportunity to sit down and work with the REST API. This week the opportunity finally came up so I decided to develop a .Net client to hopefully make working the TableAPI in .Net dead simple. My goal was a client that was not tied to any particular integration project and would be easy to move between projects. Hopefully this can be of some use to someone else.
Thanks! Great point on using app.config, in a real app that is where I would prefer that as well. I will claim that I left the settings directly in the demo project to keep it straightforward and focused on the client usage, but to be perfectly honest I was just being lazy there . Your idea of adding a record count is a good one, in fact, that could probably be useful in a lot of scenarios so I think I'll go ahead and add it to the response object. 2b1af7f3a8