Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Switching Dataset backends quickly
Message
From
01/08/2007 03:49:34
 
 
To
31/07/2007 11:53:02
General information
Forum:
ASP.NET
Category:
ADO.NET
Environment versions
Environment:
VB 8.0
OS:
Windows Server 2003
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01243434
Message ID:
01245112
Views:
41
Part of what attracted me to this thread was the admonishment not to use table adapters. They seem counter intuitive to me. I would have expected to call datatable.update() or dataset.update() and have the object update itself.

I already have my primary dataset subclassed. Do you think it would be a bad idea to add fill, insert, update methods directly to that class?

I was thinking that if I did it that way it would simplify the logic of my program and make it easier to hook in things like biz objects and data access layers as I develop them.


>>Hmm... I think what I'm not getting is what the .XSD is used for. I had assumed it was used by the IDE for creating the DataSet.Designer.cs file, are you using the .XSD at run time in your programs?
>
>No, you're right. The .xsd is used by the IDE to generate a Typed DataSet. I was just talking about another way of creating the .xsd (programmatically with a utility). End result is the same.
>
>>I appreciate your help on this, there is so much to understand when you are getting ready to write decent sized apps in a new language. Understanding the basics of how to lay things out in the new system really helps!
>
>No problem, you're welcome. Starting out with the correct architecture right from the beginning certainly makes developing a new app much easier! =0)
>
>~~Bonnie
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform