title: What components to use for ASP.Net Web site re-architecture
body: <p>I am tasked with re-architecture an existing ASP.Net 2.0 Web Site. The current solution has 3 projects; Web UI, Business layer project and Data layer project.  </p>
  
  <p>The Data layer uses some sort of SQL helper class and stored procedures to return DataTable.</p>
  
  <p>The Business layer sort of passes the DataTable along, I don't see much business logic.</p>
  
  <p>The UI web site is heavy on DataGrids.</p>
  
  <p>While brainstorming, my thoughts are; I want to obviously keep the layered design and use the separation of code by using 3 projects in the solution.</p>
  
  <p>The part that I am most confused about is the Data Layer.<br>
  What should I use for this part, Entity Framework, or create my own Classes that represent my database or logical objects?
  Speed of development is also an issue, it has to be down fairly quickly and be flexible or decoupled for enhancements.</p>
  
  <p>I tried going the MVC route but the learning curve is too steep for the developers at this time. So, it has to be Web Forms. :-(</p>
  
  <p>I am leaning on using Enterprise Library for Data access, logging, caching and Exception handling.</p>
  
  <p>I am seeking suggestions and best practices.</p>