title: Why does Microsoft Test Manager expect test DLL's under a bin/debug folders structure?
body: <p>When I attempt to run automated tests via Microsoft Test Manager, I get the error </p>
  
  <blockquote>
    <p>"Cannot find the test" .... "with storage '..\bin\debug\mytest.dll".</p>
  </blockquote>
  
  <p>Why is it looking in there? </p>
  
  <p>By build agent working directory is C:\MyBuildOutput, so when a build is run, the DLL's are output to C:\MyBuildOutput\Binaries. </p>
  
  <p>So why does Microsoft Test Manager expect to find the DLL's under C:\MyBuildOutput\bin\debug ? </p>
  
  <p>I haven't told Microsoft Test Manager to look there, and in fact my build definition build process parameters build my solution in Release mode! </p>
  
  <p>I can get it to work by getting a script to create a bin and debug folder and copying the DLL's in there - but that's just plain inconvenient!! </p>
  
  <p>I think it also expects the bin and debug folder even when I specify a custom build directory using the Microsoft Test Manager command-line utility (tcm.exe). </p>
  
  <p>I'm grateful to hear any explanations, solutions, ideas or thoughts! </p>
  
  <p>Thanks</p>
  
  <p>EDIT: As per solution below, MS Test Manager DOES NOT EXPECT test DLL's under a bin/debug folder (although the error message does almost imply it). </p>