troubleshooting Question

MSB3061: Unable to delete file "bin\Debug\<<DLLName>>". Access to the path '<<ReferencePNE>>' is denied

Avatar of GouthamAnand
GouthamAnand asked on
.NET Programming
2 Comments1 Solution3927 ViewsLast Modified:
Hi,

I'm having problems compiling my project in Visual Studio 2010.
After I compile the first time (after startup), I can't compile a second time because all the DLLs reference appears to be locked. I am not using any source control.
My project is very simple project.

Below is my build output.

 
------ Clean started: Project: WEHinters, Configuration: Release Any CPU ------
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\WEHinters.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\WEHinters.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\WEHinters.pdb". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\WEHinters.pdb' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Remote.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Remote.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Remote.Framework.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Remote.Framework.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Configuration.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Configuration.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Exceptions.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Exceptions.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Framework.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Framework.dll' is denied.
c:\WINNT\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(3607,9): warning MSB3061: Unable to delete file "f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Utils.dll". Access to the path 'f:\visual studio 2010\Projects\WEHinter\WEHinter\bin\Release\GSL.Shared.Utils.dll' is denied.
========== Clean: 1 succeeded, 0 failed, 0 skipped ==========
ASKER CERTIFIED SOLUTION
AndyAinscow
Freelance programmer / Consultant

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 2 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros