Dev environment not releasing control of .exe
-
I am using VS2008 on XP and I'm having trouble with the debugger fully terminating the process of my application after I am done debugging. Basically, the machine still thinks the exe is running so that I or the compiler cannot delete the file, leaving me unable to recompile. The problem seems to happen at completely random times and I am not able to reliably reproduce it. I have run ProcessExplorer and can see when the devenv starts the process and seems to release it. It does not appear to be running anywhere else. The program is fairly small (few hundred lines) and deals with writing a few things to the registry and logging events with the NT event log. I'm recently upgraded to VS2008 (new program though) and have never had this problem before. Any insights or troubleshooting tips would be appreciated. Thanks, Dustin P.S. Rebooting obviously fixes the problem, but I can't afford to do that 10 times a day.
-
I am using VS2008 on XP and I'm having trouble with the debugger fully terminating the process of my application after I am done debugging. Basically, the machine still thinks the exe is running so that I or the compiler cannot delete the file, leaving me unable to recompile. The problem seems to happen at completely random times and I am not able to reliably reproduce it. I have run ProcessExplorer and can see when the devenv starts the process and seems to release it. It does not appear to be running anywhere else. The program is fairly small (few hundred lines) and deals with writing a few things to the registry and logging events with the NT event log. I'm recently upgraded to VS2008 (new program though) and have never had this problem before. Any insights or troubleshooting tips would be appreciated. Thanks, Dustin P.S. Rebooting obviously fixes the problem, but I can't afford to do that 10 times a day.
-
Are you able to delete the file manually in such situations....?
No, it was completely locked. However, I just figured out the problem. Apparently, after you open an event created be the application the event viewer opens the exe to access the message resources in the file. I didn't figure this out before because simply having the event log open doesn't cause the problem, you must open the actual event. The event viewer remains in control of the exe until the whole thing is closed, not just the event. I was sure I tried that before but I guess I didn't. Thanks anyways, Dustin