title: Why is my code found even after I moved it to a subfolder?
body: <p>I embarked upon a refactoring of the file structure of my app, as it has various clearly-defined sections, and putting them in various folders would make the whole thing more grokkable/maintainable. </p>
  
  <p>I thought I was going to run into problems when I created folders in Visual Studio, moved *.cs files into them, and then tried to compile. But no, VS didn't so much as peep, and it ran fine.</p>
  
  <p>To be more specific, I created a folder below my project named "SharedCode" I then dragged a file named SQLDBHelper.cs into that folder (I didn't copy it, I moved it). I thought the references to the code in it, such as:</p>
  
  <pre><code>DataTable dtPriceComplianceResults = SQLDBHelper.ExecuteSQLReturnDataTable(ReportRunnerConstsAndUtils.SUMMARY_STOREDPROC, . . .
  </code></pre>
  
  <p>...were going to stop working, since they formerly found that file on the same level (directly below the Project, "ReportRunner") and now it's in "ReportRunner\SharedCode"</p>
  
  <p>But it took the move in stride - compiled, and successfully made the call when I ran the app.</p>
  
  <p>I was also kind of expecting that Visual Studio (or Resharper?) would change this, in SQLDBHelper:</p>
  
  <pre><code>namespace ReportRunner
  </code></pre>
  
  <p>...to this:</p>
  
  <pre><code>namespace ReportRunner.SharedCode
  </code></pre>
  
  <p>...but it didn't. Why did this work seamlessly, and does it mean that I can create other project folders and drag files into their willy-nilly and expect all the code to still know where to look to find code it calls?</p>
  
  <h2>UPDATE</h2>
  
  <p>Although it compiles and runs fine, when I let the Resharper hounds loose on it (via Resharper > Inspect > Code Issues in Solution), I get some fingerwags along these lines:</p>
  
  <pre><code>Project ReportRunner
    PriceCompliance\PriceComplianceRpt.cs:13 Namespace does not correspond to file location, should be: 'ReportRunner.PriceCompliance'
  </code></pre>
  
  <p>If I acquiesce, and let Resharper "fix the problem," the namespace changes from "<em>namespace ReportRunner</em>" to "<em>namespace ReportRunner.PriceCompliance</em>"</p>
  
  <p>But since all works fine without this change resharpening of the namespace, what benefit does appending the folder name to the namespace have?</p>