By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,680 Members | 2,139 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,680 IT Pros & Developers. It's quick & easy.

Typed Dataset vs Classes - XSD.exe

P: n/a
Good Morning;

I am collecting feedback on typed datasets vs class representation
implementation using automated code generated by XSD.exe. I can see the
benefits for a typed dataset for a rich UI application but do not see it for
non UI driven applications using the obejects. Inheritence.. etc.. Can
anyone direct me to some good info or thoughts about the subject.

Thanks
-Joe
Nov 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"BeanTownBizTalkGuru" <Be*****************@discussions.microsoft.com> wrote
in message news:89**********************************@microsof t.com...
Good Morning;

I am collecting feedback on typed datasets vs class representation
implementation using automated code generated by XSD.exe. I can see the
benefits for a typed dataset for a rich UI application but do not see it
for
non UI driven applications using the obejects. Inheritence.. etc.. Can
anyone direct me to some good info or thoughts about the subject.


You've pretty much got it.

DataSets offer
automatic change tracking and marshaling for your objects.
data binding
sorting and filtering

Classes offer
simpler representation
maximum performance for single object instances

The DataSet's features support the Fetch, Filter, Sort, Add/Update/Delete,
Save workflow. If your this is what your applicaion does, then wether or
not it has a UI, the DataSet will save you time.

David
Nov 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.