With the release of the Windows Azure SDK 1.3, the Windows Azure team delivered some awesome features, such as allowing the hosting of multiple sites under one web role, the “ExtraSmall” VM instance, the ability to remote desktop directly into your web and worker roles running in the azure fabric in the cloud, the “VM role” which matches Amazon’s clunky EC2, and much more.
But the azure 1.3 SDK also introduced some problems, which I’ve blogged about in different articles. Below you can see some of the problems and solutions I propose -
- How to fix the error: “The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state” when running a Windows Azure project in the local development fabric/emulator
http://blog.ehuna.org/2011/02/how_to_fix_the_error_the_commu.html - How to fix the errors “[UnauthorizedAccessException: Access to the path '[{Guid}-mswapd-lock' is denied.]” or “"Response is not available in this context"" when using Azure Diagnostics 1.3 in a web role hosted in full IIS with multiple sites
http://blog.ehuna.org/2011/02/how_to_fix_the_errors_unauthor.html - How to automate the creation of a Windows Azure 1.3 package in Team Foundation Server (TFS) for a web role hosted in ‘Full IIS’ with multiple sites
http://blog.ehuna.org/2011/02/how_to_automate_the_creation_o.html
I thought it would be a good idea to list them out – hopefully all of these issues will be addressed when the azure sdk 1.4 is released!
Comments