title: Visual Studio 2008 locks custom MSBuild Task assemblies
body: <p>I'm developing a custom MSBuild task that builds an <a href="http://en.wikipedia.org/wiki/Object-relational_mapping" rel="noreferrer">ORM layer</a>, and using it in a project. I'm being hampered by Visual Studio's behaviour of holding onto MSBuild task DLLs and not letting go. </p>
  
  <p>I'd like to organize my solution like this;</p>
  
  <pre><code>My Solution
   |
   +- (1) ORM Layer Custom Task Project
   |  |
   |  +- BuildOrmLayerTask.cs     // here's my task
   |  
   +- (2) Business Logic Project  // and here's the project that uses it.
      |
      +- &lt;UsingTask TaskName="BuildOrmLayerTask" AssemblyFile="$(TaskAssembly)" /&gt;
  </code></pre>
  
  <p>However, when project (2) builds, it locks onto the assembly from project (1). So now I can't build project (1) again without closing the solution and re-opening it. </p>
  
  <p>Is there any way I can organize things so that the custom build task is not kept locked by Visual Studio?</p>