I was recently working on a ASP.NET MVC3 proof of concept application. My client wanted to be able to preview my work with daily builds. It was suggested that the simplest way for me to go about this would be to deploy it to Azure. This turned out to work fairly well, but I did have a few dramas getting things to work.
The main problem that I had was making sure that I deployed all of the MVC assemblies along with my app. This is required as it isn’t part of the .net framework. I found a few sites indicating which assemblies were needed, but I found I had to add a few more to list before things worked. This was a frustrating process, because I had to wait 15mins every time a tried something that didn’t work before I knew that it wasn’t going to work.
To hopefully save others from having the same problem I have included a list of the assemblies I had to deploy along with my app to get it working. To include a referenced assembly in the deployment make sure that Copy Local option is set to True in the properties of assembly reference.
Without further ado the assemblies you should include are:
- Microsoft.Web.Infrastructure
- NuGet.Core
- System.Web.Helpers
- System.Web.Mvc
- System.Web.Razor
- System.Web.WebPages
- System.Web.WebPages.Administration
- System.Web.WebPages.Deployment
- System.Web.WebPages.Razor
- WebMatrix.Data
I was quite surprised to see NuGet.Core and WebMatrix.Data in there as I can’t quite see why the MVC framework should have dependencies on these, but my application did fail to start trying to load these assemblies if I didn’t include them, so it would appear that it was necessary.
No comments:
Post a Comment