A
Andrea Vincenzi
Help me please, I'm totally stuck!
My Visual Studio 2003 debugger stopped working after I installed
Windows XP Service Pack 2. Here is what happens (with any project,
even a "Hello, world" message): the first time I open a project and
try to start it in debug mode, Visual Studio hangs before executing
the first line of code. The only way to stop it is to kill the process
using the Task Manager.
If I open the same project a second time and try to execute or build
it, I get two build errors (substitute xxx with my application name):
"Could not copy temporary files to the output directory"
"The file ‘xxx.exe' cannot be copied to the run directory. The process
cannot access the file because it is being used by another proc"
This is probably just a side effect, due to the fact that on the first
execution attempt the two files "xxx.exe" and "xxx.pdb" have been
created, and now they are locked.
I'm almost sure that this behavior was caused by the installation of
Windows XP Service pack 2, because before that everything was working
fine. This is not the sort of thing that makes a developer happy,
especially when he's on a tight schedule…
My Visual Studio 2003 debugger stopped working after I installed
Windows XP Service Pack 2. Here is what happens (with any project,
even a "Hello, world" message): the first time I open a project and
try to start it in debug mode, Visual Studio hangs before executing
the first line of code. The only way to stop it is to kill the process
using the Task Manager.
If I open the same project a second time and try to execute or build
it, I get two build errors (substitute xxx with my application name):
"Could not copy temporary files to the output directory"
"The file ‘xxx.exe' cannot be copied to the run directory. The process
cannot access the file because it is being used by another proc"
This is probably just a side effect, due to the fact that on the first
execution attempt the two files "xxx.exe" and "xxx.pdb" have been
created, and now they are locked.
I'm almost sure that this behavior was caused by the installation of
Windows XP Service pack 2, because before that everything was working
fine. This is not the sort of thing that makes a developer happy,
especially when he's on a tight schedule…