Day 6. Building Strongly Typed DataSet Classes

for RuBoard

Day 6. Building Strongly Typed DataSet Classes

Yesterday you completed a three-day, in-depth look at how a DataSet and its related classes function by examining how the DataSet tracks its changes. At this point, you should have a good understanding of how to work with a DataSet in disconnected scenarios and both its functionality and limitations.

Today's short lesson will focus on extending the base DataSet class using the inheritance features built into the common language runtime in order to create custom DataSet classes. The custom classes are easier for developers to work with because they provide a more object-oriented means to access the data in the DataSet . In addition, they reduce programming errors introduced at design time by providing a strongly typed DataSet class with which to work. Today, we'll also examine techniques for persisting a DataSet to disk and passing it between tiers in a distributed application.

To that end, today you'll learn the following concepts:

• The purpose and goals of a strongly typed DataSet

• How to create a strongly typed DataSet both programmatically and graphically in VS .NET

• How a strongly typed DataSet is versioned and can be shared between projects

• How a DataSet can be serialized and passed between tiers using .NET Remoting

for RuBoard