Getting ERROR While building
<p>All was fine for a while. Then, all out of the blue, Visual Studio failed to build when I was about to launch the application. I got the warning "Unable to delete file '...bin\Debug[ProjectName].exe'. Access to the path '...bin\Debug[ProjectName].exe' is denied." and the error "Unable to copy file 'obj\x86\Debug[ProjectName].exe' to 'bin\Debug[ProjectName].exe'. The process cannot access the file 'bin\Debug[ProjectName].exe' because it is being used by another process." (I get both the warning and the error when running Rebuild, but only the error when running Build - don't think that is relevant?)</p>

<p>I understand perfectly fine what the warning and error message says: Visual Studio is obviously trying to overwrite the exe-file while it the same time has a lock on it for some reason. However, this doesn't help me find a solution to the problem... The only thing I've found working is to shut down Visual Studio and start it again. Building and launching then works, untill I make a change in some of the forms, then I have the same problem again and have to restart... Quite frustrating!</p>

<p>As I mentioned above, this seems to be a known problem, so there are lots of suggested solutions. I'll just list what I've already tried here, so people know what to skip:</p>

<p>Creating a new clean solution and just copy the files from the old solution.
Adding the following to the following to the project's pre-build event:</p>

<pre><code>if exist "$(TargetPath).locked" del "$(TargetPath).locked" 
  if not exist "$(TargetPath).locked" if exist "$(TargetPath)" move "$(TargetPath)" "$(TargetPath).locked"
</code></pre>

<p>Adding the following to the project properties (.csproj file):</p>

<pre><code>&lt;GenerateResourceNeverLockTypeAssemblies&gt;true&lt;/GenerateResourceNeverLockTypeAssemblies&gt;
</code></pre>

<p>However, none of them worked for me, so you can probably see why I'm starting to get a bit frustrated. I don't know where else to look, so I hope somebody has something to give me! Is this a bug in VS, and if so is there a patch? Or has I done something wrong, do I have a circular reference or similar, and if so how could I find out?</p>

<p>Any suggestions are highly appreciated :)</p>

<p>Update: As mentioned in comment below, I've also checked using Process Explorer that it actually is Visual Studio that is locking the file.</p>
