all groups > dotnet general > june 2004 >
You're in the

dotnet general

group:

Strongly Typed DataSets


Re: Strongly Typed DataSets William Ryan eMVP
6/2/2004 8:42:36 PM
dotnet general:
Depends but they have many benefits, mainly Intellisense, Ease of use and
Performance.

If you only have one table, then using just one table is fine. The
difference is trivial but you'll be fine either way.

--
W.G. Ryan MVP Windows - Embedded

http://forums.devbuzz.com
http://www.knowdotnet.com/dataaccess.html
http://www.msmvps.com/williamryan/
[quoted text, click to view]

Strongly Typed DataSets Jim Douglas
6/2/2004 10:15:44 PM
Are they worth the trouble? Are folks using these for single table
processing? What would you choose, Dataset vs Datatable for single table.

Thanks

--

Jim Douglas
http:\\www.genesis-software.com

Latitude 32.5818
Longitude -96.5412
Elevation 497




Re: Strongly Typed DataSets Cor Ligthert
6/3/2004 9:26:14 AM
Hi Jim,

In addition to Bill, an answer on your second part of your question.

With the dataset you have a lot of build in methods to serialize.
(Webservice, read/write direct to XML etc).

I think that that makes the decission.

Cor

[quoted text, click to view]

Re: Strongly Typed DataSets Nick Holmes
6/3/2004 2:54:19 PM
They are worth the trouble, but only just, IMHO. The problem is not the idea
(which is great), but the implementation of them. They aren't as good as
they could be. The good news is that there are a couple of alternative
generators out there, and writing your own generator is not that hard.

We use them for both single and multiple table situations. Even for single
tables, we stick to using a complete DataSet.

Nick Holmes.


[quoted text, click to view]

AddThis Social Bookmark Button