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 220.127.116.11
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 18.104.22.168.
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.
What I have tried that didn't work
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=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35' matches 'System.Web.Mvc, Version=126.96.36.199, 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="188.8.131.52-184.108.40.206" newVersion="220.127.116.11" /> </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?