How does one go about installing ASP.NET MVC 4 on a server. The Web Platform Installer insists on installing all kinds of Visual Studio 2010 stuff. I don't see a "server only" installation. For example, it wants to install "Visual Studio 2010 Core SP1" and "Visual Web Developer Express".
-
Wrong StackExchange site. Try here next time. serverfault.comPluc– Pluc2012-08-21 17:24:35 +00:00Commented Aug 21, 2012 at 17:24
-
3You should not be doing that. You should be using the ASP.NET MVC 4 nuget package which will add all needed assemblies as Copy Local Always so when you deploy it will include them all as part of the site/applicationIvan Zlatev– Ivan Zlatev2012-08-22 21:38:16 +00:00Commented Aug 22, 2012 at 21:38
-
To add: This is a big deal because once you have it in GAC it will always override the local version which can lead to bizzare problems when updates come!Ivan Zlatev– Ivan Zlatev2012-08-22 21:59:19 +00:00Commented Aug 22, 2012 at 21:59
Add a comment
|
3 Answers
Get the standalone installer from http://www.asp.net/mvc/mvc4
11 Comments
Aaron Jensen
This is not a great option. The standalone installer is intended to be installed with Visual Studio 2010. We don't run Visual Studio 2010. We need an installer that at most gets the MVC v4 assemblies in to the GAC. They are in the GAC on the build servers, so don't get copied to the bin at compile time. It's frustrating that Microsoft still isn't thinking about operational concerns.
Aaron Jensen
Yes. I've tried it. But it makes our operations team nervous. They don't know what kind of side-affects the installer has: what additional stuff it installs that they don't know about.
Lucero
@splatteredbits, if your operations team is any good they can monitor the changes made by the install, and by doing so on a virtual test machine they don't run any risk whatsoever. I bet that many of the hotfixes delivered via Windows Update are more suspect in what they do than this installer.
Moulde
Yeah, don't use the web platform installer for installing on the server. Use the above standalone mvc4 installer. Works great for me :)
|
The safest thing to do would be to mark your reference to System.Web.Mvc as "copy local = true" in the reference's properties window. When you do a deploy, it will get copied into your bin folder.
It feels a bit backwards, but there you go.
1 Comment
Cornelius
Or more approriately, install the MVC nuget package, which does this for you. Which, in turn, is not at all backwards, because it allows coexistence of different versions, so each project can be sure it gets the version it was built against. Having it in the GAC would override this.
I would install and run on local host, then use Visual Studio's "publish" to publish it to a web server. You can install it via http://www.asp.net/mvc. If you're asking how to install it on IIS, then read this: