Azure Storage Client (v2.0) - Disposing resources...

Question

What are the suggest best practices around disposing resources when working with Blob storage particularly with Managed client APIs ver 2.0 ?

None of the following components implement IDispoable (or a Close() method).

1. CloudStorageAccount
2. CloudBlobClient
3. CloudBlobContainer
4. CloudBlockBlob

Short of reviewing the source, where can I learn more about best practices around releasing resources?

Thx in adv

  

 

Answer 1

Hi, what do you mean by disposing resources when working with Blob storage? Delete blobs?

If your answer is yes, then you can follow below workthroughs to archieve it.

http://www.windowsazure.com/en-us/develop/net/how-to-guides/blob-storage/

http://blogs.msdn.com/b/jnak/archive/2010/01/11/walkthrough-windows-azure-blob-storage-nov-2009-and-later.aspx

http://blogs.msdn.com/b/avkashchauhan/archive/2011/07/29/programatically-deleting-older-blobs-in-windows-azure-storage.aspx

Best Regards

Answer 2

Not looking for deleting or archiving blob storage content.

The question is more about releasing resources that may be held by Storage Client (eg: http connections, streams, if any). Looking at the source code of storage client, pretty much all operations seem to use transient resources.

Answer 3

Hi,

those resources are released automatically by the storage client library, because they're created by the library. For example, using Reflector to review the code, you may notice:
executionState.RestCMD.ResponseStream.Dispose();
And:
executionState.Resp.Close();
When designing your own class library, it is also a good idea to dispose the resources you created (but not resources created by the caller).

Best Regards