Dino Esposito ha escrito un artículo super con respecto a la evolución de ADO y sus componentes.
How were you writing data access code five years ago? You were likely using ADO Recordsets, that is a fairly bloated object incorporating well three distinct functionalities–server cursor, disconnected client cursor, firehose-style cursor.
Then came ADO.NET with its popular pair–DataSet and DataReader. Five years ago, the DataSet was hailed as a greatly enhanced version of the ADO Recordset. Five years ago, writing a custom collection was mostly possible through ATL but data binding in ASP application was still a dream (or a nightmare, from another perspective). Then .NET FX came with its predefined set of collection classes, DataSet, and typed DataSets.
Which one is your favorite? And more importantly, which one is the favorite for your application? As a matter of fact, the advent of the .NET Framework 2.0 and generics enables developers to generate and manage collections much more quickly and effectively then in the recent past. Still a number of other considerations apply. You can read my two cents on MSDN Magazine.
Cheers!
Deja una respuesta
Lo siento, debes estar conectado para publicar un comentario.