We have an ASP.NET MVC 4 solution with a couple of references that has been building without problems for about 2 years now. However, after installing KB2993928 and KB2993937 th
This was done by a security update on October 15th from Windows Update. You will need to run the updates on your build servers too.
Link to update: http://www.microsoft.com/en-ie/download/details.aspx?id=44533
This update fixes other versions as well.
You will likely have to update your projects to the newer version, as it changes the version number and removes the older version completely.
Remove any references to System.Web.MVC and then re-add them by manually browsing to the dll (C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Web.Mvc\v4.0_5.1.0.0__31bf3856ad364e35\System.Web.MVC.dll on our machine). A lot faster than re-installing MVC if this has just taken your production server down!
If this issue is caused by references which in turn have dependencies on those specific assemblies, you can remedy this by coercing FxCop to use only the StrongName and ignore the version number. This solution is described here.
Of course the real solution would be to update the referenced assemblies (with the indirect dependencies) to newer versions.
The security updates update the assembly version of system.web.mvc.dll. You need to update your csproject to correct the version. Check this post: ASP.NET MVC security patch to version 3.0.0.1 breaks build
Solution:
Should fix the problem - no changes to the build/solutions is required.
I used the following solution and it's work perfectly:
https://stackoverflow.com/a/26490590
(don't forget to select the default project on the Package Manager Console for each project with the build failed)