title: Visual studio 2008 dataset generation issue (namespace issue)
body: <p>At work we use typed dataset in some projects for our DataAccess layer. Sometimes we extend them using the partial class feature : using View code on a dataset create a DataSetName.cs with the partial class declaration where you can add code. Inside this file we also add the TableAdapter partial class.</p>
  
  <p>Recently we migrated on Visual Studio 2008 from VS 2005. The behavior of the dataset generator seems to be different in VS 2008. It removed a part in the TableAdapter namespace in the .cs file :</p>
  
  <p>Example : </p>
  
  <p>Original code :</p>
  
  <pre><code>
  namespace ClassLibrary1.Dataset.DataSet1TableAdapters  
  {  
     public partial class CategoriesTableAdapter  
     {  
     }  
  }
  </code></pre>
  
  <p>After migration in VS 2008 :</p>
  
  <pre><code>
  namespace ClassLibrary1.DataSet1TableAdapters  
  {  
     public partial class CategoriesTableAdapter  
     {  
     }  
  }
  </code></pre>
  
  <p>The namespace changed ! It has been replaced by the root namespace of the project.</p>
  
  <p>Reproduction steps :</p>
  
  <ol>
  <li>Create a class library project.</li>
  <li>Add a folder called Dataset or whatever in the project.</li>
  <li>Add a dataset inside the folder (DataSet1).</li>
  <li>Drop a table in the dataset designer (I used a table from Northwind).</li>
  <li>Right click on the dataset in the Solution Explorer and choose View Code. It will create a DataSet1.cs file with a partial class of the dataset inside.</li>
  <li>Copy the namespace and class for the table adapter from DataSet1.Designer.cs and paste it inside DataSet1.cs.</li>
  <li>Run custom tool on the dataset, it works !</li>
  <li>Close solution</li>
  <li>Open the solution again</li>
  <li>Run custom tool on the dataset, namespace modified for the tableAdapter, very annoying :(</li>
  </ol>
  
  <p>My Machine :
  Windows Server 2003 R2 Standard Edition SP2
  Visual Studio 2008 Pro (9.0.21022.8 RTM)
  Also tested on a colleague's computer running XP.</p>
  
  <p>Anyone already experiencied the same weird behavior ?
  Did I made something wrong ? 
  Is there something new to configure inside Visual Studio 2008 to make it works like it did in VS 2005 ?</p>