title: Create Project Dependency and Add Reference to Project still causes "The type or namespace name could not be found"
body: <p>I have a solution in Visual Studio 2010 containing 6 projects (1 web application, 4 c# class libraries, 1 c# console application).</p>
  
  <p>The console application is my test harness and use this to test external web services, output from methods from within my other libraries and general experimentation.  This test console application has only one dependency on another project dependency, one of the C# libraries.</p>
  
  <p>The referenced C# library is pretty simple:</p>
  
  <pre><code>namespace GowallaAPI
  {
      public class Gowalla
      {
         private static readonly ILog log = LogManager.GetLogger(typeof(Gowalla));
         public SpotsInRadius GetGowallaSpotsInRadius(decimal lat, decimal lon, int radius) {
             //snip
         }
         //other methods removed for brevity//
      }
  }
  </code></pre>
  
  <p>I have added to my console application a project reference:</p>
  
  <p><img src="https://i.stack.imgur.com/N7ghg.jpg" alt="enter image description here"></p>
  
  <p>And I've also right-clicked on References and selected Add Reference...</p>
  
  <p><img src="https://i.stack.imgur.com/3z6hf.jpg" alt="you can see the Gowalla reference already exists in this example picture"></p>
  
  <p>Then, I've gone to my console application and added;</p>
  
  <pre><code>using Gowalla;
  </code></pre>
  
  <p>Then hit build. I get this:</p>
  
  <blockquote>
    <p>The type or namespace name 'Gowalla'
    could not be found (are you missing a
    using directive or an assembly
    reference?)</p>
  </blockquote>
  
  <p>I am completely baffled. I have:</p>
  
  <ol>
  <li>Remove the dependencies completely (and then rebuilt with Gowalla references removed), and added them again.</li>
  <li>I have removed the dependencies completely (like #1) and then added them as assemblies only (Add Reference...).</li>
  <li>Checked that the target framework for both console application and class library is .NET 4.0 - they are.</li>
  <li>Checked that all necessary items within the Gowalla class library are marked as Compile in the Build property.</li>
  <li>Jiggled the build order of the project so that I am at least building the console application AFTER the library is built.</li>
  <li>Done some shouting and swearing.</li>
  <li>Given up and then returned.</li>
  <li>Moved the Gowalla C# library out to its own project entirely and then referenced the assembly (like in 2).</li>
  <li><p>Playing the having a constructor in Gowalla and not:</p>
  
  <p>public Gowalla()
  {</p>
  
  <p>}
  ... and nothing has worked!</p></li>
  </ol>
  
  <p>Can anyone see something obvious? Am I being utterly stupid? I have been on this for hours and I wonder quietly if this is a classic 'wood for the trees' moment...</p>
  
  <p>Help appreciated.</p>
  
  <p><strong>EDIT 1:</strong> This is the Gowalla.dll exposed from Reflector:</p>
  
  <p><img src="https://i.stack.imgur.com/JC1Gi.jpg" alt="enter image description here"></p>
  
  <p><strong>ANSWER:</strong> After @gov's helpful suggestion to remove the GowallaAPI library and try and add something else I did that and started adding in the old code from the GowallaAPI library.  Everything worked until I added:</p>
  
  <pre><code>private static readonly ILog log = LogManager.GetLogger(typeof(Gowalla));
  </code></pre>
  
  <p>log4net for some utterly bizarre reason kept throwing the build.  Alas, after removing the line (the reference to log4net remains), the project built and worked perfectly thereafter. Thank you to @gov for setting me on the right path! :D</p>