title: Why are circular references in Visual Studio a bad practice?
body: <h1>Why are circular references in Visual Studio a bad practice?</h1>
  
  <p>First, I will describe an example of how this can happen using C# in Visual Studio, since VS will typically inform you if you have a circular reference and prevent it.</p>
  
  <p>First, a <strong>Utilities</strong> class is created relying only on the code given to you by Visual Studio and .Net. Then, an <strong>E-mail</strong> class is created that depends on <strong>Utilities</strong>. Instead of adding both projects to a single solution, a new solution is created and a reference to <em>Utilities.dll</em> is added. Then, some time later, someone decides that they want the <strong>Utilities</strong> class to send an e-mail and adds a reference to <em>Email.dll</em>. Visual Studio is perfectly happy to let you do this, but now the source won't compile as-is without one of the binaries.</p>
  
  <p>At my place of work it is standard procedure to copy-and-paste binaries when doing development and then only building the projects you're working on. This has led to at least one circular reference in the codebase that has gone unnoticed for over 3 years.</p>
  
  <p>This seems like a very bad practice to me because there is no way to build either project from source without having the DLLs first. That argument falls a little flat to the "practical" people I work with since it seems highly unlikely that we will lose all copies of our binaries simultaneously. The binaries aren't stored in version control at any point, which only makes me more worried.</p>
  
  <p>This seems like a situation that should be avoided, but not a situation that poses any appreciable threat. <strong>Are circular references between projects really a big deal or am I blowing it out of proportion?</strong></p>