title: Visual Studio reference another project under development and release configuration
body: <p>I have 2 solutions that I'm currently developing. One solution is my main application which has a few projects inside it (DAL, BL, UI and CORE) as layers, and the second solution is a class library that I'm developing (that can be used by any project and not only my first solution) - the first solution uses that class library.</p>
  
  <p>Since my second solution (the class library) is still also under development (and the best way to test it is on a read developing app), in the first solution I have a reference to the Debug DLL of the second solution - so when I make changes to the second solution while working I can already see them affect the real application.</p>
  
  <p>What I'm wondering about is what is the best practice to work in such a case? and when publishing my first solution (the application) how do I make it only for publishing take the Release version of the DLL and not the Debug one that I pointed to? </p>