title: c# using declarations - more = good or bad?
body: <p><em>edit</em> typos</p>
  
  <p>Hi, </p>
  
  <p>This is possibly a moronic question, but if it helps me follow best practice I don't care :P</p>
  
  <p>Say I want to use classes &amp; methods within the System.Data namespace... and also the System.Data.SqlClient namespace.</p>
  
  <p>Is it better to pull both into play or just the parent, ie...</p>
  
  <pre><code>using System.Data
  using System.Data.SqlClient
  </code></pre>
  
  <p>or just...</p>
  
  <pre><code>using System.Data
  </code></pre>
  
  <p>More importantly I guess, does it have ANY effect on the application - or is it just a matter of preference (declaring both the parent and child keeps the rest of the code neat and tidy, but is that at the detriment of the application's speed because its pulling in the whole parent namespace AND then a child?)</p>
  
  <p>Hope thats not too much waffle </p>