Geeks With Blogs

News QTP and Stuff
Theo Moore Questions... Morphology? Longevity? Incept dates?

Spent several hours today trying to extend an existing typeddataset in VS 2005. I like typeddatasets for the most part, but they can be annoying with which to work. The one in question has about 50 tables in it. To be honest, I've not used them a ton. However, 50 tables seems a bit....unwieldy to me. Does this seem like a lot?

Some random things I've thought about them: 1) they seem awfully fragile. They break faster than the iPhone. 2) trying to get the error out of one once you fill your DataAdapter can be a real pain, too. You can catch the error on the table in the dataset itself, thank goodness. 3) Extending them is kind of a pain. Use them on data that you don't expect to change a lot. Trying to add new stuff involves some significant moving parts.

Anyway, they are great for serialization of course, and that's what we are using them for. Just seems to me that there is trade-off to be had in maintainability. Just my two cents.

Posted on Monday, July 9, 2007 10:11 PM | Back to top


Comments on this post: TypedDataSets: so many moving parts

# re: TypedDataSets: so many moving parts
Requesting Gravatar...
I agree with you, datasets in general are difficult to maintain.

For reasons you've stated, and a few more, is why I prefer to use POCOs.
Left by Jason Whitehorn on Jul 09, 2007 10:30 PM

Comments have been closed on this topic.
Copyright © Theo Moore | Powered by: GeeksWithBlogs.net