Windows Azure Development
Archive for May, 2010
Remember to update your DiagnosticsConnectionString before deploying
May 28th
In the ServiceConfiguration.cscfg file, you have a DiagnosticsConnectionString which as a default is linked to local storage.
<Setting name="DiagnosticsConnectionString" value="UseDevelopmentStorage=true" />
When you deploy your package it will never start correctly (stuck in Busy/Initializing), because you could will be trying to log to the local storage, which doesn’t exist in the cloud.
Fixing this is easy:
- Create a storage account if you don’t already have one.
- In Visual Studio, bring up the properties of your project, then click settings.
- Click on the … next to the DiagnosticsConnectionString.
- Enter your storage details in the dialog.
- Save then deploy.
THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS
address is not the same as Address
May 4th
When using Windows Azure table storage – keep in mind the property names are case sensitive!
Yesterday one of our developers was working on refactoring some code. As is standard practice, they changed the class properties on the table storage entity classes from a lower case address to an upper case Address. This worked fine in the developer fabric, but when we pushed to the cloud the app broke. Upon investigation it turned out each entity now had an address property as well as the new Address property.
Easy fix, we changed everything back to lower case.
THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS EVEN IF YOU HAVE A NOTE FROM YOUR MUM