Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio - Cannot build a simple project more than once
    text
    copied!<p>When I try to build a project twice in successon, i get the following error</p> <pre><code>Error 2 Unable to copy file "obj\x86\Release\iFileUploader.exe" to "bin\Release\iFileUploader.exe". The process cannot access the file 'bin\Release\iFileUploader.exe' because it is being used by another process. </code></pre> <p>If I close Visual Studio and reopen it, I can compile it again but only once.</p> <p>I have my projects hosted on a Windows network share. The server runs Windows 2008 R2 and Im on a Windows 7 machine and Ive tried setting everyone full control on the share and the folder permission, to no avail.</p> <p>Ive even run the Unlocker program and checked the Windows Share &amp; Storage Manager to see if anything is using it and nothing is! I cant delete the file when this happens either until I close VS.</p> <p>Is there a setting I am missing in Visual Studio?!</p> <hr> <p><strong>UPDATE</strong></p> <p>Have removed all antivirus/antispam, disabled firewall.. so zero security.</p> <p>Have disabled "Enable the Visual Studio hosting process"</p> <p>Visual Studio is some how the colprupt with not releasing the handle</p> <p><img src="https://i.stack.imgur.com/l5luV.png" alt="enter image description here"></p> <p><img src="https://i.stack.imgur.com/KSA7N.png" alt="enter image description here"></p> <hr> <p><strong>UPDATE</strong></p> <p>Another thread that has exactly the same problem but from years ago !!</p> <p><a href="https://stackoverflow.com/questions/2817525/destroy-process-less-console-windows-left-by-visual-studio-debug-sessions">Destroy process-less console windows left by Visual Studio debug sessions</a></p> <hr> <p><strong>UPDATE</strong></p> <p>I copied the files locally, and that didnt work. So I created a new project and then copied all the code in to the new project and now its working (with the files stored locally)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload