http://blogs.msdn.com/brada/archive/2009/07/09/net-rocks-on-data-access-options.aspxRecently .NET Rocks! talked to Stephen Forte and covered a topic I have been interested in for a a couple of years: Data Access Options .&#160; Clearly this has been a space of a lot of innovation in the last few years.&#160; Stephen does a good job ofen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/brada/archive/2009/07/09/net-rocks-on-data-access-options.aspx#9868393Thu, 13 Aug 2009 18:14:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:9868393Marc Schluper<p>I like this topic too. I am still using ADO.NET because it is sufficient and waited for the time that others had figured out what's best to use. It looks like this time has come. Finally a discussion on what to use when.</p> <p>Now in his interview Stephen says that using Silverlight with ADO.NET (and WCF) is ugly because it would involve DataSets. I use (like John Papa shows in his book - Ch. 6) DataReaders to create generic lists. Nothing ugly about that. A bit more typing (I guess), but that takes less than 5% of all development time. </p> <p>Can we conclude that if the database tables closely reflect the application domain entities, ADO.NET works just fine (and fast)?</p>