tags:

views:

17653

answers:

3
+8  A: 

Installing MVC directly on your web server is one option, as then the assemblies will be installed in the GAC. You can also bin deploy the assemblies, which might help keep your server clear of pre-release assemblies until a final release is available.

Phil Haack posted a nice article a couple days ago about how to deploy MVC along with your app, so it's not necessary to install directly:

http://www.haacked.com/archive/2008/11/03/bin-deploy-aspnetmvc.aspx

Matt Rudder
Wow. Simul-post with the author. Thanks.
Zack Peterson
+25  A: 

I just wrote a blog post addressing this. You could install ASP.NET MVC on your server OR you can follow the steps here.

Haacked
Thank you, Phil.
Zack Peterson
Thank you too, Phil! I remember reading that article last year and had originally setup my "bin-deployment" just fine back then, but forgot all about it until I just upgraded from MVC 1.0 to 2 and found (after deploying to production!) that the "Copy Local" settings on these had all been reset to false! Quickly fixed, quickly re-deployed. Thanks again!
Funka
This is exactly what I needed, thanks much!
MrBoJangles
A: 

I have the MVC installed on locally and I STILL get this error... This is a new error.

Jemer99
Someone with a lot of reputation points remove this post, please.
MrBoJangles