We have an old ASP.NET MVC 3 Web Application, building in VS2010, that fails to compile, since last week's security update.
The problem is that the reference to System.Web.Mvc.dll is broken.
When I open the solution file on our build machine, where the security update has not run, and open the properties dialog for References->System.Web.MVC, it looks just fine.
Path is C:\Program Files\Microsoft ASP.NET\ASP.NET MVC 3\Assemblies\System.Web.Mvc.dll Version is 188.8.131.52
But when I open the solution file on a dev machine where the security update has run, References->System.Web.MVC is flagged as missing. If I remove it, and try to add it back using VS2010's Add Reference dialog, it doesn't show.
Wandering around the web has led me to suggestions involving updating MVC using NuGet. We didn't use NuGet, in our VS2010 projects, so that doesn't seem quite right, for this situation. I tried it anyway, and ended up with half-a-dozen missing references.
When I look at the properties for "C:\Program Files\Microsoft ASP.NET\ASP.NET MVC 3\Assemblies\System.Web.Mvc.dll" in Windows Explorer, on the build machine I see version 184.108.40.206.
When I look at the properties on the dev machine, I see version 3.0.50813.1.
What I need is a way to change the way I build and run so that I can build and run regardless of which of these two DLLs in installed in the .NET 3.0 framework.
First attempt - if the assembly is missing, add it. I deleted the old missing reference. Then I copied the DLL from the "ASP.NET MVC3\Assemblies" folder, into a folder in my project. Set it as "Copy Always", and added it as a reference.
With that, the project would compile in VS2010, but when I'd try to precompile the pages with aspnet_compiler, I got warnings:
(0): warning CS1702: Assuming assembly reference 'System.Web.Mvc, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35' matches 'System.Web.Mvc, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31bf3856ad364e35', you may need to supply runtime policy
So far, I've been able to manage to avoid understanding runtime policies, but I tried to add this, in the web.config:
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="22.214.171.124-126.96.36.199" newVersion="188.8.131.52" /> </dependentAssembly> </assemblyBinding> </runtime>
Tried it again, and got the same warnings.
My question is - do I still have a problem? Or will my resolve it, despite the warnings?
Had this problem in vs2017, I already got MVC via nuget but System.Web.Mvc didn't appear in the "Assemblies" list under "Add Reference".
The solution was to select "Extensions" under "Assemblies" in the "Add Reference" dialog.
Get the latest version of MVC3 via NuGet. Open your project in Dev Studio. Open the Package Manager Console tab at the bottom of Dev Studio. Then use this command:
PM> Install-Package Microsoft.AspNet.Mvc -Version 3.0.50813.1
If you click the tab key after "-Version" you will get a list of all of the available versions.
If you have an old version of NuGet you may get an error indicating you have to upgrade it. If so, open Tools->Extension Manager to install the latest version of NuGet. Note, you will need to run Dev Studio as Administrator before you can install NuGet.
Installing MVC3 should update Web.config in your project.
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="0.0.0.0-184.108.40.206" newVersion="220.127.116.11" /> </dependentAssembly> </assemblyBinding>
Add the reference again from ./packages/Microsoft.AspNet.Mvc.[version]/lib/net45/System.Web.Mvc.dll
Just in case someone is a position where he get's the same error. In my case downgrading Microsoft.AspNet.Mvc and then upgrading it again helped. I had this problem after installing Glimpse and removing it. System.Web.Mvc was references wrong somehow, cleaning the solution or rebuilding it didin't worked in my case. Just give it try if none of the above answers works for you.
In my case I had all of the proper references in my project. I found that by building the solution the nuget packages were automatically restored.
The sample mvcmusicstore.codeplex.com opened in vs2015 missed some references, one of them System.web.mvc.
The fix for this was to remove it from the references and to add a reference: choose Extentions under Assemblies, there you can find and add System.Web.Mvc.
(The other assemblies I added with the nuget packages.)
I have the same situation: Visual Studio 2010, no NuGet installed, and an ASP.NET application using System.Web.Mvc version 3.
What worked for me, was to set each C# project that uses System.Web.Mvc, to go to References in the Solution Explorer, and set properties on System.Web.Mvc, with Copy Local to true, and Specific Version to false - the last one caused the Version field to show the current version on that machine.
Easiest way to solve this problem is install ASP.NET MVC 3 from Web Platforms installer.
Or by using Nuget command
Install-Package Microsoft.AspNet.Mvc -Version 3.0.50813.1
in VS 2017 I cleaned the solution and rebuilt it and that fixed it
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Stack 5\Packages\ Microsoft.AspNet.Mvc.5.0.0\lib\net45\System.Web.Mvc.dll
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET MVC 4\Assemblies\System.Web.Mvc.dll
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET MVC 3\Assemblies\System.Web.Mvc.dll
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET MVC 2\Assemblies\System.Web.Mvc.dll