I just had to debug the problem when Asp.Net seemed to cache the dlls of the projects referenced by the site, even after they were restored
The solution compiles, but at runtime, Asp.Net refers to an outdated binary in C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ Temporary ASP.NET Files \ root and throws an exception. (I don’t think that a specific exception is relevant, but just the fact that the base code is old, in my case it is a problem with LLBLGEN, where entity indices are out of order)
This is a new problem, but it seems to constantly work on development workstations and on our integration server, so I think it should be some kind of configuration.
We are developing against Asp.Net 4, on IIS 7.5
Update
We use the optimizeCompilations flag in the system.web / compilation element in web.config. I don’t see how this can affect it, but I would turn it over and see if anything changes.
source share