Use of datasets?

[jby1]

Hi

I am working on a new ASP.NET project. The data access method that has been proposed is a method used quite commonly in VB projects, ie to have a class for each data entity containing a set of properties, and a class which corresponds to the collection of entities. This class handles the access to the database (via a DataReader), maintaining the collection of entities etc. DataSets have not been used anywhere in this model.

Personally I would prefer to use DataSets and the recognised .NET way of managing the data. However, the main reason I have for this is because I want to get the experience for myself. Can anybody give me a better technical reason (perhaps even an overview of the best way of doing this!)? Or is the proposed way of doing it ok?

Thanks for any replies.

 

[stsuing]

6, 1/2 dozen. Did it both ways, both have benefites and drawbacks. Choose one and be consistent.

My personal opinion is that the way you describe is best for large complicated systems, where OO principals are needed.

The dataset route is best for writing straight forward applications in the shortest amount of time.

You should play with the datasets, but don't dicount your expirence with the OO method.

 

[BoulderBum]

The first method (custom objects) tend to have a performance advantage over conventional DataSets, but DataSets far outweigh the first approach in flexibility.

DataSets can maintain complex relationships in a standardized way, easily merge with other data, easily integrate with other ADO.NET objects like a SqlDataAdapter for easy inserts/updates, etc. and more.

 

[jby1]

Thanks a lot for those replies, that has helped me a lot. I have decided that we should stick with the OO approach for now. I may try and work some DataSets in somewhere though, just for the experience ;-)