I have an MVC project thats been working perfectly until I updated my machine a week ago. I now receive a Binding Error when trying to run the project
Managed Debuggin
We encountered a similar problem by deploying assemblies generated by ASP.NET from a developer machine to a production environment (referring to assemblies generated for .ascx and .aspx controls which are compiled at runtime).
We are (hackishly) copying and persisting such runtime generated assemblies from ASP.NET temporary compile folders (ie. "C:/Users/[USER]/AppData/Local/Temp/Temporary ASP.NET Files/") to avoid some recompiling as the service boots, in order to improve performance. However using assemblies compiled on a dev machine introduces dependencies to VisualStudio assemblies.
We fixed it by letting the production environment generate these assemblies on its own. We are copying and persisting these 'production' assemblies instead and the problem vanishes entirely.
Make sure you are not doing such awkward use of ASP.NET generated assemblies and it will probably fix it.