title: Window Update Broke MVC Application
body: <p>I ran Windows Update yesterday and its introduced some problems when I'm trying to release a new version of my ASP.NET MVC 4 project.</p>
  
  <p>The application compiles and runs okay locally, however when I push the version up to a test-site on my webserver it fell over with the error message:  </p>
  
  <pre><code>System.Web.HttpCompileException: (0): error CS1705: Assembly 'App_Code, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'System.Web.Mvc, Version=4.0.0.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
  </code></pre>
  
  <p>After some research I found that this is due to an update from 4.0.0.0 to 4.0.0.1.  I removed the System.Web.Mvc dll from my project and readded the dll that has the later version.  Again everything works locally but not on the web.  I then went through the web.config's and changed any mention of 4.0.0.0 to 4.0.0.1.  Likewise this continues to work internally but fails externally.  The error message is:</p>
  
  <pre>    
  Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) 
  
  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
  
  Exception Details: System.IO.FileLoadException: Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
  
  Source Error: 
  
  An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  
  
  Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
  
  WRN: Assembly binding logging is turned OFF.
  To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
  Note: There is some performance penalty associated with assembly bind failure logging.
  To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
  
  </pre> 
  
  <p>I believe this has something to do with Elmah that I'm using for the error handling.  </p>
  
  <p>I tried to reinstall from Nuget as suggested here: <a href="https://stackoverflow.com/questions/26393157/windows-update-caused-mvc3-and-mvc4-stop-working">Windows update caused MVC3 and MVC4 stop working</a> but that hasn't worked and I'm getting the same error.</p>
  
  <p>Added info:
  The server hasn't yet been updated, I'm concerned that updating this might break the existing live version.</p>