title: Resolving another project's renamed assembly dependency
body: <p>I have a solution in which I needed to brand an assembly for a third-party client. This resulted in a class structure as follows:</p>
  
  <pre><code>Project1
    References
      MyBrandedAssembly.dll (namespace: MyAssembly)
  Project2
    References
      Project1
  </code></pre>
  
  <p>When MsBuild built <code>Project1</code>, it could resolve the <code>MyAssembly</code> namespace to <code>MyBrandedAssembly.dll</code>:</p>
  
  <pre><code>Primary reference "MyAssembly".
    Resolved file path is "SolutionPath\Binaries\MyBrandedAssembly.dll".
    Reference found at search path location "{HintPathFromItem}".
  </code></pre>
  
  <p>But when building <code>Project2</code>, it could not resolve the second-order reference:</p>
  
  <pre><code>Dependency "MyAssembly".
    Could not resolve this reference. Could not locate the assembly "MyAssembly". 
     Check to make sure the assembly exists on disk. If this reference is required by your  
     code, you may get compilation errors.
      For SearchPath "SolutionPath\Project1\bin\Debug".
      Considered "SolutionPath\Project1\bin\Debug\MyAssembly", but it didn't exist.
  </code></pre>
  
  <p>Why not? And how can I force it to?</p>