Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

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

Posted on 2013-11-13
2
Medium Priority
?
3,391 Views
Last Modified: 2013-11-14
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 ==========
0
Comment
Question by:GouthamAnand
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 45

Accepted Solution

by:
AndyAinscow earned 1500 total points
ID: 39647299
A couple of points that might result in this error.
There are two copies of visual studio running with the same project open in each.
The exe is actually running outside of visual studio when you attempt the second build - so using the dll's which prevents them being deleted.
0
 

Author Closing Comment

by:GouthamAnand
ID: 39648018
Thanks a lot.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The object model of .Net can be overwhelming at times – so overwhelming that quite trivial tasks often take hours of research. In this case, the task at hand was to populate the datagrid from SQL Server database in Visual Studio 2008 Windows applica…
Welcome my friends to the second instalment and follow-up to our Minify and Concatenate Your Scripts and Stylesheets (http://www.experts-exchange.com/Programming/Languages/.NET/ASP.NET/A_4334-Minify-and-Concatenate-Your-Scripts-and-Stylesheets.html)…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question