Unable to copy file "obj\x86\Debug\MatListControls.exe" to "bin\Debug\MatListControls.exe". when starting a second debugging session

Unable to copy file "obj\x86\Debug\MatListControls.exe" to "bin\Debug\MatListControls.exe". when starting a second debugging session by Rob Perkins

Closed

as Fixed

Type:	Bug
ID:	463894
Opened:	6/3/2009 5:04:22 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

See problem steps recorder file. I've noticed two other reports related to this message, closed because the testers "cannot duplicate".

*I* can duplicate it here. Contact me for a LiveMeeting and I'll let you drive this VM

Details (expand)

English

Visual Studio 2010 Beta 1

Windows 7 RC

English

See problem steps recorder file.

Error 3 Unable to copy file "obj\x86\Debug\MatListControls.exe" to "bin\Debug\MatListControls.exe". The process cannot access the file 'bin\Debug\MatListControls.exe' because it is being used by another process. MatListControls

start of a debug session without this error.

File Name	Submitted By	Submitted On	File Size
Unable to copy file because it is being used by another process.zip (restricted)	Rob Perkins	6/3/2009	-

Posted by Tom John [RF] on 7/25/2010 at 10:43 AM

Getting this issue on VS2010 RTM - of the 3-4 "workarounds" on the web, only restarting VS solves the problem. Happy to do a LM if anyone wants to take a look. Can reproduce every single time.

Posted by Microsoft on 7/31/2009 at 10:47 AM

Thanks for following up with this in the face of the initial "no repro". We have fixed this bug for Beta2. It was also found internally and is an important bug to fix.

Posted by Microsoft on 7/31/2009 at 1:16 AM

Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team

Posted by Jonathan Dickinson on 7/7/2009 at 8:10 AM

Restart Visual Studio.

Posted by Jonathan Dickinson on 7/7/2009 at 8:38 AM

It looks like disabling background compilation resolves this:
1. Tools -> Options
2. Expand "Text Editor"
3. Expand "C#"
4. Click "Advanced"
5. Under "Editor Help" clear the check next to "Show live semantic errors"

Posted by MarkLIC on 5/20/2010 at 1:23 PM

I've been repeatedly getting this error as well. It seems to have gone away completely since I added a pre-build step to run Unlocker on the target file:

"C:\Program Files\Unlocker\Unlocker.exe" $(TargetPath) /D /S