>>>>
>>>>DataSets are not so bad. Just think of them having most of the features of databases, except in memory and not directly linked to the database.
>>>>
>>
>>
>>Just to throw a fly in the ointment, you'll need to start learning the entity framework and linq.... I don't think ADO is long for this world.
>
>But the Entity Framework uses ADO.NET. Quote:
>Under the covers, the mapping provider will use the EDM schema and the mapping/view information to translate to and from the conceptual model. Then it'll use a regular ADO.NET provider to talk to the underlying database (e.g. it would use System.Data.SqlClient to talk to a SQL Server database).


I understand that... I've got Julie Lerman's book. However; I think all ADO ops will eventually be encapsulated by the EF so that will become the norm. I don't think writing ADO.net code in programs will be around in the future. That's what I'm trying to say.