VS2005 Dataset Designer - dataenvironment hell reborn or a reliable tool?

  • Thread starter Thread starter philmcin
  • Start date Start date
P

philmcin

I have been reading about the new data features in VB 2005, and while
the DataSet Designer promises to reduce development time, it also looks
very much like the VB6 DataEnvironment which, for me at least, was a
source of much grief which went away when I replaced it with straight
ADO code, as well as being rather inflexible when changes are required.

Can anybody tell me if the time saved writing less code with the
DataSet Designer is going to just be postponed to support and bug fixes
or is it really time saved creating reliable apps?
 
I'll preface this with saying that I haven't played with the 2005 designer
yet.

I'm sure using the VS designers make it quicker to write a particular
screen.
However, between the unnecessary code that gets generated, maintenance
headaches, and the fact that the generated code is not reusable in a generic
manner - I personally can't imagine a serious production application being
written using those wizards.

I think the wizards are good as a way to get started and learn, but in my
personal opinion they should not be used to write actual applications.
 
Back
Top