469,953 Members | 2,400 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,953 developers. It's quick & easy.

Receiving Error: Unable to copy file "obj\Debug\MyProject.xml" to "bin\Debug\MyProject.xml". Access to the path 'obj\Debug\Aegis.xml' is denied. Aegis

Hi,

We have just started getting the following error during compiles of our
forms-based application. We are developing in VS2008, VB.Net, with Team
Foundation Server-based source control.

Full error message is:
"Unable to copy file "obj\Debug\OurProjectName.xml" to
"bin\Debug\OurProjectName.xml". Access to the path
'obj\Debug\OurProjectName.xml' is denied."

This error has just started happening in our project in the last couple
days. It is intermitant and affecting all developers in our team. The only
way to get around it that we know of is to shut down/restart VS2008. It
will be fine for a few hours and then out of the blue start happening again.

Has anyone out there had a similar experience and found a solution?

Thanks
Mar 14 '08 #1
2 5784
FWIW, I've seen this same problem. I just took a quick look at the Microsoft
Connect website (the official place to provide product feedback -
http://connect.microsoft.com/VisualStudio) and I didn't see this exact problem.
That doesn't mean it hasn't been reported. More than likely my search criteria
didn't pick it up. Can someone else confirm whether or not this bug has been
reported?

Bob
Mar 15 '08 #2
"CGatto" <cg****@pleaseremoveme.gnb.cawrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
Hi,

We have just started getting the following error during compiles of our
forms-based application. We are developing in VS2008, VB.Net, with Team
Foundation Server-based source control.

Full error message is:
"Unable to copy file "obj\Debug\OurProjectName.xml" to
"bin\Debug\OurProjectName.xml". Access to the path
'obj\Debug\OurProjectName.xml' is denied."

This error has just started happening in our project in the last couple
days. It is intermitant and affecting all developers in our team. The
only way to get around it that we know of is to shut down/restart VS2008.
It will be fine for a few hours and then out of the blue start happening
again.

Has anyone out there had a similar experience and found a solution?

Thanks
Just an update on the issue for anyone who comes across the same thing. We
seem to have eliminated the problem but in a round-about way that we don't
quite understand. It seems as though our application had several unused
references in place which we removed (via Project Properties References >
Unused References Remove). One of those references was to a dll called
OurProjectName.dll located in the bin folder of the project. Why it was
there we do not know and no one can recall adding it in. Since it has been
removed the error has not occured again.
Mar 27 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Ferd Biffle | last post: by
2 posts views Thread by DartmanX | last post: by
1 post views Thread by Winterminute | last post: by
43 posts views Thread by Christoph Schneegans | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.