ASP.NET MVC 2 and Windows Azure

image If you upgrade an Azure web instance to use ASP.NET MVC 2, make sure you mark the System.Web.Mvc reference as Copy Local = true.  Otherwise, your deployment will fail.  And you won’t get any good feedback from Windows Azure as to the cause of the problem.  So you’ll start searching the web for help, and perhaps you’ll stumble on this post, and you’ll realize that you didn’t set Copy Local = true on your System.Web.Mvc assembly reference in your ASP.NET MVC 2 web instance.  And you’ll  leave happy (or at least slightly happier) than when you came.

That is all.

5 Comments

  • tower defense said

    Thanks for this post :) I read about this on some forum but I forgot what do I need to change;) Hopefully I found your blog in google and now my deployment works correct :)

  • egipt said

    I'm trying to run an existing ASP.NET MVC 2 application in the development fabric (1.2) using VS2010 on Windows 7. I'm following the Windows Azure Platform Training Kit Hands-On Labs (June 2010 update). When hitting F5 I see a blank screen.
    I also tried to create a completely new solution, starting with a new cloud service and adding a new MVC web role. This works, but only when the MVC WebRole targets .NET Framework 3.5. After changing this to .NET Framework 4.0 again a blank screen appears.
    Did anyone have the same issues ?

Add a Comment