When hitting a breakpoint in ASP.Net 2.0, I get warnings like:
Cannot open output assembly '<some path>Config.dll ' for Edit and Continue:
The system cannot find the file specified.
That's entirely reasonable, because the "Config" project is not set to compile
(as there are no items that need compiling).
But why is VS2005 even trying to access that (non-existent) dll?
The applications works, it's just an annoying message.
Hans Kesting