You can deploy MVC3 to Azure, endure you have all these in the reference and copy local set to true:

• Microsoft.Web.Infrastructure
• System.Web.Helpers
• System.Web.Mvc
• System.Web.Razor
• System.Web.WebPages
• System.Web.WebPages.Deployment
• System.Web.WebPages.Razor

The best way to debug this after a deployment is to have the following in the web.config for debugging purposes:

<system.web>
  <customErrors mode="Off" />
  <compilation debug="true" targetFramework="4.0">

 

Obviously do not have this for production!

Hi,

I am working on a project with Team Foundation Server which loves to make the web.config file read only. When this occurs and I try to run my MVC3 ASP.NET web role, I will get this error:

"The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state."

It is not the best error in the world, however, the Development Fabric is deploying the application and needs write access to your web.config file, so endure this is not Read Only.

I never have this issue with BitBucket and Mecurial

Honestly, I think this is a bug with the SDK 1.3, as I have this problem with other projects like Windows Phone 7 and Azure connectivity, what happens it it keeps playing with the machine key!

<machineKey decryption="AES" decryptionKey=blahblahblah