Data Access Strategy with ASP.NET

[imterpsfan3]

I have been using mostly datareader with command objects to load data on webforms from a dataset. I then update, delete or insert using a command object with stored procedure.

I recently went on an interview for an ASP.NET position and they were looking for someone to convert existing ASP to ASP.NET. They seemed to think my strategy was wrong and that one should use mostly cached datasets. Needless to say I didn't get the job, but that is neither here nor there.

I would like an opinion from other people as to how they view this subject. I have read benchmark tests done by Microsoft and it showed quite a difference in performance in using datareaders as opposed to datasets. And that there was a problem sometimes synchronizing data in the backend database if you are using cached datasets.

I know there is a time and a place for cached datasets.

 

[imterpsfan3]

This link below is some food for thought. I read this AFTER my above post. Scott Mitchell is recognized as one of the foremost .net developers in the country.

http://aspnet.4guysfromrolla.com/articles/050405-1.aspx

 

[imterpsfan3]

I made a mistake in the first post. I said "I have been using mostly datareader with command objects to load data on webforms from a dataset"...I meant to say from a datareader based off of a command object.