SV: [DOTNET-WINFORMS] Help set the direction for Microsoft's data technologies

Benny Skjold Tordrup <[email protected]> Sat, 17 Nov 2007 10:41:32 +0100
Newsgroups gmane.comp.windows.devel.dotnet.winforms
Message-ID <03ae01c828fe$0982cb30$1c886190$@net>
Just completed the survey and actually missed a "General comments" question
:-)

When creating DataSets in VS 2005, I always delete the TableAdapter class
created in the dataset. IMO it does not belong there.

If you rely on DataSets as the data structure definition in a n-tier
application, the DataSet classes would be used in most tiers - especially
the UI layer. Having TableAdapters in the DataSet definition would force DAL
code to flow around in the UI layer - where it does not belong.

The practice that I use, is the DataSet definition in one library and the
actual DataAccess classes (DAL) in another library.

Med venlig hilsen / Best regards





-----Oprindelig meddelelse-----
Fra: Discussion forum for developers using Windows Forms to build apps and
controls [mailto:[email protected]] På vegne af Erick
Thompson
Sendt: 16. november 2007 22:10
Til: [email protected]
Emne: [DOTNET-WINFORMS] Help set the direction for Microsoft's data
technologies

We are seeking feedback and information on the way that you build
applications so that we can continue to improve Microsoft developer
products.



In particular, we are looking for developers of all stripes to take a survey
that gathers information about how you write n-tier, traditional, or web
service oriented applications that deal with data. The survey is fairly
short, and should not take more than a few moments of your time. Your
assistance in taking this survey will help us make better informed decisions
on future versions of Microsoft developer technologies.



If you complete the survey, you will be entered for a random drawing for
some nice Microsoft swag. Responses will remain confidential, although you
will be asked if we can contact you for more information.



http://tinyurl.com/2ryq6b



Thank you for your assistance,



Erick Thompson

ADO.NET Program Manager