Comments on: I understand DataSets. What is a TableAdapter for? http://dotnetting.wordpress.com/2007/02/04/i-understand-datasets-what-is-a-tableadapter-for/ .NET tips, tricks, discussion Mon, 06 Apr 2009 03:58:07 +0000 http://wordpress.com/ hourly 1 By: salohcin http://dotnetting.wordpress.com/2007/02/04/i-understand-datasets-what-is-a-tableadapter-for/#comment-6 salohcin Tue, 06 Feb 2007 18:53:26 +0000 http://dotnetting.wordpress.com/2007/02/04/i-understand-datasets-what-is-a-tableadapter-for/#comment-6 I'd appreciate it if you could point me to some articles/evidence that backs your claim up about DataSets. In the application I'm writing now, I attempted to go the route of using DataSets and TableAdapters, followed by hooking up web list controls with ObjectDataSource objects. In the end I ditched this approach because the auto-generated code couldn't handle the GUIDs I was using in my database. The drag'n'drop way of building things scares me a little if I'm truthful. I found myself having to jump through a lot of hoops in order to get the desired results. Though I must say that the auto-generated stored procedures is a nice touch. I'm wondering if i can get Visual Studio to generate just the stored procedures on their own rather than having to go through the motions of creating DataSets and TableAdapters then deleting them? I'm going to follow your advice for now and write code with the keyboard. Learning this way will ensure I understand what's going on under the hood. I've used DataReader objects in my DALs to get data from the database, custom objects and generic collections that hook up to Repeaters to display my data. I'd like to find out when it is appropriate to use the visual part of Visual Studio. Any one care to fill me in? I’d appreciate it if you could point me to some articles/evidence that backs your claim up about DataSets.

In the application I’m writing now, I attempted to go the route of using DataSets and TableAdapters, followed by hooking up web list controls with ObjectDataSource objects. In the end I ditched this approach because the auto-generated code couldn’t handle the GUIDs I was using in my database.

The drag’n'drop way of building things scares me a little if I’m truthful. I found myself having to jump through a lot of hoops in order to get the desired results. Though I must say that the auto-generated stored procedures is a nice touch. I’m wondering if i can get Visual Studio to generate just the stored procedures on their own rather than having to go through the motions of creating DataSets and TableAdapters then deleting them?

I’m going to follow your advice for now and write code with the keyboard. Learning this way will ensure I understand what’s going on under the hood. I’ve used DataReader objects in my DALs to get data from the database, custom objects and generic collections that hook up to Repeaters to display my data.

I’d like to find out when it is appropriate to use the visual part of Visual Studio. Any one care to fill me in?

]]> By: cmv http://dotnetting.wordpress.com/2007/02/04/i-understand-datasets-what-is-a-tableadapter-for/#comment-5 cmv Mon, 05 Feb 2007 04:07:06 +0000 http://dotnetting.wordpress.com/2007/02/04/i-understand-datasets-what-is-a-tableadapter-for/#comment-5 Datasets are absolutely not worth learning and not worth your time. the only benefit (maybe) is code generation, which is piss poor at best. just look into the class that gets created, look in OnInit and you'll notice that every object in the dataset is instantiated in OnInit, regardless if it will ever be used! Datasets are for "Drag and Drop" developers. Please do not go down that road. Datasets are absolutely not worth learning and not worth your time. the only benefit (maybe) is code generation, which is piss poor at best. just look into the class that gets created, look in OnInit and you’ll notice that every object in the dataset is instantiated in OnInit, regardless if it will ever be used! Datasets are for “Drag and Drop” developers. Please do not go down that road.

]]>