Scott doesn't use datasets in ASP .NET Applications
By Eric Wise
I generally prefer business objects and collections thereof for a good chunk of my ASP .NET applications. This is mostly because by extending business objects with properties, methods, and events I can gain a level of control that isn't possible with the dataset. Using a datareader to populate these objects is fast and easy.
However... in the case where I am just displaying data, such as binding results to a combo box or showing a summary grid, I tend to use a datatable or dataset.
……
URL: http://codebetter.com/blogs/eric.wise/archive/2005/05/02/62743.aspx
***
I have almost the same ideas with this guy. In the meanwhile, I also support the following idea.
Any DataLayer must be a simple code block, that they allow operations against DB.
That code block would not have to know on the Business Entities. Single to specialize it is to execute the operations (Store Procedures and SQL Sentences) against the engine DB (SQL, Oracle, DB2, etc.), with which this setting.