New DataSet Features in ADO.NET 2.0

My article on the new DataSet features in ADO.NET 2.0 has gone live on MSDN.

From the Introduction:

This article is actually the first of two articles on the DataSet and associated classes in ADO.NET 2.0. Here we will focus on the classes in the .NET Framework. In the subsequent article, we will focus on developing with these and related classes from within the Visual Studio 2005 development environment. Visual Studio 2005 offers several designers and tools that offer tremendous flexibility and productivity for developing the data-centric aspects of your application. As a result, each article will have a different "feel". This article is mainly an overview of new functionality, accompanied by explanations and code samples. In the next article, the focus is more on the development process, as we see how to develop a working application.

Published Saturday, November 06, 2004 7:03 PM by Jackie Goldstein
Filed under: ,

Comments

Tuesday, November 23, 2004 5:43 AM by avnrao

# re: New DataSet Features in ADO.NET 2.0

very good article. but i have a clarification..
Table 1. Summary of Load Semantics lists the status of DataRow after Load operation. the cell for Unchanged-PreserveCurrentValues displays current as <incoming>..should it not show as <existing> and the state as the state of Unchanged-UpdateCurrentValues.
Monday, November 29, 2004 4:53 PM by Jackie Goldstein

# re: New DataSet Features in ADO.NET 2.0

avnrao,

It definitely is "non-obvious" but that is the way it is designed. The way to understand it is as follow: The purpose of the PreserveCurrentValues option is to update the original values of the data, presumably in prepartion for performing an update of the current values against the original DB. In this case, it will update the original value to the incoming value. I order to maintain the state as Unchanged, the current value is also set to the incoming value.