title: Would a ORM fit my purpose
body: <p>We usually write stored procedures on the database which accepts xml and returns result set as xml. I am thinking of providing a abstraction for the database calls like below</p>
  <h3>Example</h3>
  <pre><code>    public List&lt;Person&gt; GetAllPeople()
      {
          string requestXml = &quot;&lt;Request&gt;&lt;Type&gt;GetAllPeople&lt;/Type&gt;&lt;/Request&gt;&quot;;
          //execute a procedure with above xml as input
          //load the response xml into dataset
          //foreach record instantiate Person &amp; add to list
          return List&lt;Person&gt;();
      }
  </code></pre>
  <p>so that the team can work with strongly typed objects rather loosly coupled Xml Strings. I think this is the work that ORM does right? Or should i code my own Data access layer to return objects rather than dataset and datatables. So the question is</p>
  <ul>
  <li><p>Will ORM suit this type of data access?</p>
  </li>
  <li><p>What would right path to follow for abstracting database calls?</p>
  </li>
  </ul>
  <h3>Specs</h3>
  <p>SQL Server 2005, .NET 2.0, ASP.NET 2.0, C# 2.0</p>