Ronald,
Personally, I like everything in DataSets, as I don't like having to
write up all the code for my data container. I also prefer to have the
operations on the data separated from the data container itself, given that
I find it fits more with transactional processing.
However, that's not an argument against using your own objects, and
possibly placing methods to perform work on those objects. DataSets have
their own shortcomings. Particularly, for large sets of data, they can be
inefficient, and managing relations isn't as intuitive as using an object
heiarchy.
There are many more pros and cons to each side. What are your
requirements or concerns? It would probably be easier to work from those as
opposed to asking for a side-by-side comparison.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Ronald S. Cook" <rc***@westinis.comwrote in message
news:ea**************@TK2MSFTNGP02.phx.gbl...
We're designing an app and see two basic ways to return data from the
business tier to the client:
1) Everything in DataSets
2) Fill properties of objects and manage accordingly
Any opinions as to overall approach?
Thanks.