In case you hadn’t noticed, the Storage Client sample in the SDK is no longer a sample – as of the November CTP it has become part of the core Azure runtime classes. This is good news for those of us who like having built-in, easy-to-use, managed wrapper around all the REST-based storage API calls. Unfortunately, the namespace and API changes mean that lots of sample code out there is now broken… But hey, that’s why it’s a CTP, right?
At any rate, the changes mean that the Azure Virtual Lab at msdev.com no longer works as is. I’ll be working on updated content that reflects the latest changes, but in the meantime you should be able to proceed with the help of the following file (luckily, I encapsulated all storage client code into a single class, so this should be a relatively easy fix.)
UPDATED: The Windows Azure Virtual Lab has now been updated to reflect the November API changes – you can check it out here.
#1 by Cory Fowler on December 10, 2009 - 9:57 am
I wrote 2 blog posts about some of the namespace changes. I also have a few more on the way about some more things that were separated. Check out http://blog.syntaxc4.net
#2 by Cory 'SyntaxC4' Fowler on December 23, 2009 - 6:30 pm
Hi Bill,
I’m taking a look at your AzureStorageClient class, there is a reference to a Globals class within the file. I can’t seem to find the namespace it belongs to. Could you point me in the right Direction?
Thanks,
Cory
#3 by bill on December 28, 2009 - 8:46 am
Hi Cory,
You’ll find the Globals class in the “VirtualLabResources.zip” file that you can download at the virtual lab site. It’s in the “Solution Items” directory, and it just defines a few string variables (specifically, it allows for defining the names of blob containers and queues in one place.)
HTH!
Bill