System.Data [00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00] 1.0.3300.0 1.0.5000.0 2.0.0.0 Gtk# is thread aware, but not thread safe; See the <link location="node:gtk-sharp/programming/threads">Gtk# Thread Programming</link> for details. System.ComponentModel.MarshalByValueComponent System.ComponentModel.IListSource System.ComponentModel.ISupportInitializeNotification System.Runtime.Serialization.ISerializable System.Xml.Serialization.IXmlSerializable System.Xml.Serialization.XmlRoot("DataSet") System.Xml.Serialization.XmlSchemaProvider("GetDataSetSchema") System.ComponentModel.Designer("Microsoft.VSDesigner.Data.VS.DataSetDesigner, Microsoft.VSDesigner, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a", "System.ComponentModel.Design.IDesigner") System.ComponentModel.DefaultProperty("DataSetName") System.ComponentModel.ToolboxItem("Microsoft.VSDesigner.Data.VS.DataSetToolboxItem, Microsoft.VSDesigner, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")

The , which is an in-memory cache of data retrieved from a data source, is a major component of the ADO.NET architecture. The consists of a collection of objects that you can relate to each other with objects. You can also enforce data integrity in the by using the and objects. For further details about working with objects, see Using DataSets in ADO.NET.

Whereas objects contain the data, the allows you to navigate though the table hierarchy. The tables are contained in a accessed through the property. When accessing objects, note that they are conditionally case sensitive. For example, if one is named "mydatatable" and another is named "Mydatatable", a string used to search for one of the tables is regarded as case sensitive. However, if "mydatatable" exists and "Mydatatable" does not, the search string is regarded as case insensitive. For more information about working with objects, see Creating a DataTable.

A can read and write data and schema as XML documents. The data and schema can then be transported across HTTP and used by any application, on any platform that is XML-enabled. You can save the schema as an XML schema with the method, and both schema and data can be saved using the method. To read an XML document that includes both schema and data, use the method.

In a typical multiple-tier implementation, the steps for creating and refreshing a , and in turn, updating the original data are to:

Build and fill each in a with data from a data source using a .

Change the data in individual objects by adding, updating, or deleting objects.

Invoke the method to create a second that features only the changes to the data.

Call the method of the , passing the second as an argument.

Invoke the method to merge the changes from the second into the first.

Invoke the on the . Alternatively, invoke to cancel the changes.

The and objects inherit from , and support the interface for remoting. These are the only ADO.NET objects that can be remoted.

Classes inherited from are not finalized by the garbage collector, because the finalizer has been suppressed in . The derived class can call the method in its constructor to allow the class to be finalized by the garbage collector.

Represents an in-memory cache of data.

- Constructor

  This implementation of the constructor takes no parameters, and creates a default name, "NewDataSet," for the new instance.

  A name for the is required to ensure that the XML representation of the always has a name for the document element, which is the highest-level element in a schema definition.

  Initializes a new instance of the class.

  1.0.5000.0
  2.0.0.0
- Constructor

  A name for the is required to ensure that the XML representation of the always has a name for the document element, which is the highest level element in a schema definition.

  Initializes a new instance of a class with the given name.

  The name of the .
  1.0.5000.0
  2.0.0.0
- Constructor

  Initializes a new instance of a class that has the given serialization information and context.

  The data needed to serialize or deserialize an object.
  The source and destination of a given serialized stream.
  1.0.5000.0
  2.0.0.0
- Constructor
  2.0.0.0
  To be added.
  To be added.

  Initializes a new instance of the class.

  The object.
  The object.
- Method
  System.Void

  Both the and classes have methods. Calling at the level causes the method for each to be called. Similarly, invoking on the causes to be called on each table within the . In this manner, you have multiple levels at which the method can be invoked. Calling the of the enables you to invoke the method on all subordinate objects (for example, tables and rows) with one call.

  When you call AcceptChanges on the DataSet, any objects still in edit-mode end their edits successfully. The property of each also changes; Added and Modified rows become Unchanged, and Deleted rows are removed.

  If the DataSet contains objects, invoking the AcceptChanges method also causes the to be enforced.

  AcceptChanges and RejectChanges only apply to DataRow related changes (that is, Add, Remove, Delete, and Modify). They are not applicable to schema or structural changes.

  Calling AcceptChanges will not replicate these changes back to the data source if the DataSet was filled using a DataAdapter. In that situation, call instead. See Updating Data Sources with DataAdapters for more information.

  Commits all the changes made to this since it was loaded or since the last time was called.

  1.0.5000.0
  2.0.0.0
- Method
  System.Void

  The Visual Studio .NET design environment uses this method to start the initialization of a component that is used on a form or used by another component. The method ends the initialization. Using the and methods prevents the control from being used before it is fully initialized.

  Begins the initialization of a that is used on a form or used by another component. The initialization occurs at run time.

  1.0.5000.0
  2.0.0.0
- Property
  System.Boolean if string comparisons are case-sensitive, otherwise. The default is .

  The property affects how sorting, searching, and filtering operations are performed on each object contained in a when using the method.

  By default, setting the property for a also sets the property of each associated to the same value.

  Gets or sets a value indicating whether string comparisons within objects are case-sensitive.

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DefaultValue(false)
- Method
  System.Void

  If the is bound to an , calling or raises the . To avoid this situation, traverse each table, removing each row one at a time.

  Clears the of any data by removing all rows in all tables.

  1.0.5000.0
  2.0.0.0
- Method
  System.Data.DataSet

  If these classes have been subclassed, the clone will also be of the same subclasses.

  Copies the structure of the , including all schemas, relations, and constraints. Does not copy any data.

  A new with the same schema as the current , but none of the data.

  1.0.5000.0
  2.0.0.0
- Method
  System.Data.DataSet If the current object is a subclass of DataSet, the clone will also be of the same type.

  Copies both the structure and data for this .

  A new with the same structure (table schemas, relations, and constraints) and data as this .

  If these classes have been subclassed, the copy will also be of the same subclasses.

  1.0.5000.0
  2.0.0.0
- Method
  2.0.0.0
  System.Data.DataTableReader

  In order to ensure the order of the result sets within the returned , if a within the is empty, it is represented by an empty result set within the returned DataTableReader.

  Returns a with one result set per , in the same sequence as the tables appear in the collection.

  A containing one or more result sets, corresponding to the instances contained within the source .

- Method
  2.0.0.0
  System.Data.DataTableReader `System.ParamArray`

  In order to ensure that the order of the result sets within the returned , if a within the is empty, it is represented by an empty result set within the returned DataTableReader. Because this overloaded version allows you to supply a list of DataTable instances as parameters, you can specify the order in which the result sets appear within the returned DataTableReader.

  Returns a with one result set per .

  A containing one or more result sets, corresponding to the instances contained within the source . The returned result sets are in the order specified by the parameter.

  An array of DataTables providing the order of the result sets to be returned in the .
- Property
  System.String The name of the DataSet object.

  Gets or sets the name of the current .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DefaultValue("")
- Property
  System.Data.DataViewManager The returned allows you to create custom settings for each contained within the DataSet object.

  The returned by the property allows you to create custom settings for each in the .

  When you obtain a from a , the sort order, filtering, and are configured according to the settings in the property.

  Gets a custom view of the data contained in the to allow filtering, searching, and navigating using a custom .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.Browsable(false)
- Method
  2.0.0.0
  System.Data.SchemaSerializationMode ``

  This method can be called when deserializing a typed to determine its .

  Determines the for a .

  An enumeration indicating whether schema information has been omitted from the payload.

  The instance that is passed during deserialization of the .
- Method
  2.0.0.0
  System.Data.SchemaSerializationMode `` ``

  This method can be called when deserializing a typed to determine its .

  Determines the for a .

  An enumeration indicating whether schema information has been omitted from the payload.

  The that a DataSet’s protected constructor is invoked with during deserialization in remoting scenarios. The that a DataSet’s protected constructor is invoked with during deserialization in remoting scenarios.
- Method
  System.Void

  The Visual Studio .NET design environment uses this method to end the initialization of a component that is used on a form or used by another component. The method starts the initialization. Using the and methods prevents the control from being used before it is fully initialized.

  Ends the initialization of a that is used on a form or used by another component. The initialization occurs at run time.

  1.0.5000.0
  2.0.0.0
- Property
  System.Boolean , if rules are enforced, otherwise. The default is .

  Constraints are set at the level ( property). For more information about creating constraints, see Adding Constraints to a Table.

  Gets or sets a value indicating whether constraint rules are followed when attempting any update operation.

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DefaultValue(true)
- Property
  System.Data.PropertyCollection A with all custom user information.

  The property enables you to store custom information with the DataSet. For example, you might store a time when the data should be refreshed.

  Extended properties must be of type if you want them persisted when the is written as XML.

  Gets the collection of customized user information associated with the DataSet.

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.Browsable(false)
- Method
  System.Data.DataSet

  Creates a new that contains a copy of all rows in the original that have pending changes. Relationship constraints can cause additional unchanged rows to be added to the new if the unchanged rows contain primary keys corresponding to foreign keys in the changed rows. The method returns null if there are no rows in the original that have pending changes.

  Gets a copy of the that contains all changes made to it since it was loaded or since was last called.

  A copy of the changes from this that can have actions performed on it and later be merged back in using . If no changed rows are found, the method returns null.

  1.0.5000.0
  2.0.0.0
- Method
  System.Data.DataSet ``

  The method is used to produce a second object that contains only the changes introduced into the original. Use the argument to specify the type of changes the new object should include.

  This returned copy is designed to be merged back in to this original . Relationship constraints may cause parent rows marked Unchanged to be included. If no rows of the desired are found, the method returns null.

  Gets a copy of the containing all changes made to it since it was last loaded, or since was called, filtered by .

  A filtered copy of the that can have actions performed on it, and subsequently be merged back in using . If no rows of the desired are found, the method returns null.

  One of the values. 1.0.5000.0 2.0.0.0
- Method
  2.0.0.0
  System.Xml.Schema.XmlSchemaComplexType `` To be added.

  Gets a copy of for the DataSet.

  A copy of .

  The specified schema set.
- Method
  2.0.0.0
  System.Void `` `` To be added.

  Populates a serialization information object with the data needed to serialize the .

  A that holds the serialized data associated with the . A that contains the source and destination of the serialized stream associated with the .
- Method
  System.Xml.Schema.XmlSchema

  Returns a serializable instance.

  The instance.

  1.0.5000.0
  2.0.0.0
- Method
  System.Void `` ``

  Deserializes the table data from the binary or XML stream.

  The instance. The streaming context. 1.0.5000.0 2.0.0.0
- Method
  System.String

  Calling this method is identical to calling with set to .

  returns XML as a string, and therefore requires more overhead than to write XML to a file.

  If you build a using schema inference and serialize it using XML or Web services, the column ordering may change.

  Returns the XML representation of the data stored in the .

  A string that is a representation of the data stored in the .

  1.0.5000.0
  2.0.0.0
- Method
  System.String

  Calling this method is identical to calling , except that only the primary schema is written.

  returns XML as a string, and therefore requires more overhead than to write XML to a file.

  If you build a using schema inference and serialize it using XML or Web services, the column ordering may change.

  Returns the XML Schema for the XML representation of the data stored in the .

  String that is the XML Schema for the XML representation of the data stored in the .

  1.0.5000.0
  2.0.0.0
- Method
  System.Boolean It is a good idea to call HasChanges before invoking .

  Gets a value indicating whether the has changes, including new, deleted, or modified rows.

  true if the has changes; otherwise false.

  1.0.5000.0
  2.0.0.0
- Method
  System.Boolean ``

  Examine the property of the DataSet before invoking the method.

  Gets a value indicating whether the has changes, including new, deleted, or modified rows, filtered by .

  true if the has changes; otherwise false.

  One of the values. 1.0.5000.0 2.0.0.0
- Property
  System.Boolean if any table contains an error, otherwise.

  Each in a also has a property. Use the HasErrors property of the DataSet first, to determine if any table has errors, before checking individual objects. If a DataTable has errors, the method returns an array of objects containing the errors.

  Gets a value indicating whether there are errors in any of the objects within this .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.Browsable(false)
- Method
  System.Void `` ``

  Applies the XML schema from the specified to the .

  The Stream from which to read the schema. An array of namespace Uniform Resource Identifier (URI) strings to be excluded from schema inference. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  Applies the XML schema from the specified to the .

  The TextReader from which to read the schema. An array of namespace Uniform Resource Identifier (URI) strings to be excluded from schema inference. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  Applies the XML schema from the specified file to the .

  The name of the file (including the path) from which to read the schema. An array of namespace Uniform Resource Identifier (URI) strings to be excluded from schema inference. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  Applies the XML schema from the specified to the .

  The XMLReader from which to read the schema. An array of namespace Uniform Resource Identifier (URI) strings to be excluded from schema inference. 1.0.5000.0 2.0.0.0
- Event
  2.0.0.0
  System.EventHandler

  For more information, see .

  Occurs after the is initialized.

- Method
  2.0.0.0
  System.Void To be added.

  Deserialize all of the tables data of the DataSet from the binary or XML stream.

- Method
  2.0.0.0
  System.Boolean `` ``

  This member supports the .NET Framework infrastructure and is not intended to be used directly from your code.

  Inspects the format of the serialized representation of the DataSet.

  true if the specified represents a DataSet serialized in its binary format, false otherwise.

  The object. The object.
- Property
  2.0.0.0
  System.ComponentModel.Browsable(false)
  System.Boolean To be added.

  Returns the status of the while it’s being constructed, for instance by Visual Studio. The method sets it to false and method sets it to true.

  Gets a value that indicates whether the is initialized.

- Method
  2.0.0.0
  System.Void `` `` `System.ParamArray`

  The method provides a technique for filling a single with data, retrieved from an instance. This method provides the same functionality, but allows you to load multiple result sets from an into multiple tables within a .

  The load operation will fail with an if any of the source data columns in the incoming are computed columns.

  The parameter allows you to specify how you want the imported data to interact with existing data, and can be any of the values from the enumeration. See the documentation for the method for more information on using this parameter.

  The parameter allows you to specify an array of instances, indicating the order of the tables corresponding to each result set loaded from the reader. The method fills each supplied instance with data from a single result set from the source data reader. After each result set, the method moves on to the next result set within the reader, until there are no more result sets.

  The name resolution scheme for this method is the same as that followed by the method of the class.

  Fills a with values from a data source using the supplied , using an array of instances to supply the schema and namespace information.

  An that provides one or more result sets. A value from the enumeration that indicates how rows already in the instances within the will be combined with incoming rows that share the same primary key. An array of instances, from which the method retrieves name and namespace information. Each of these tables must be a member of the contained by this .
- Method
  2.0.0.0
  System.Void `` `` `System.ParamArray`

  The method provides a technique for filling a single with data, retrieved from an instance. This method provides the same functionality, but allows you to load multiple result sets from an IDataReader into multiple tables within a DataSet.

  The load operation will fail with an if any of the source data columns in the incoming are computed columns.

  The parameter allows you to specify how you want the imported data to interact with existing data, and can be any of the values from the enumeration. See the documentation for the method for more information on using this parameter.

  The parameter allows you to specify an array of table names, indicating the order of the tables corresponding to each result set loaded from the reader. The Load method attempts to find a table within the DataSet matching the name found in the array of table names, in order. If a matching table is found, that table is loaded with the content of the current result set. If no matching table is found, a table is created using the name supplied in the array of table names, and the new table's schema is inferred from the result set. After each result set, the Load method moves on to the next result set within the reader, until there are no more result sets.

  The default namespace associated with DataSet, if any, is associated with each newly created DataTable. The name resolution scheme for this method is the same as that followed by the method of the class.

  Fills a with values from a data source using the supplied , using an array of strings to supply the names for the tables within the DataSet.

  An that provides one or more result sets. A value from the enumeration that indicates how rows already in the instances within the DataSet will be combined with incoming rows that share the same primary key. An array of strings, from which the Load method retrieves table name information.
- Method
  2.0.0.0
  System.Void `` `` `` `System.ParamArray`

  The method provides a technique for filling a single with data, retrieved from an instance. This method provides the same functionality, but allows you to load multiple result sets from an into multiple tables within a .

  The load operation will fail with an if any of the source data columns in the incoming are computed columns.

  The parameter allows you to specify how you want the imported data to interact with existing data, and can be any of the values from the enumeration. See the documentation for the method for more information on using this parameter.

  The parameter is a delegate that refers to a procedure that is called when an error occurs while loading data. The parameter passed to the procedure provides properties that allow you to retrieve information about the error that occurred, the current row of data, and the being filled. Using this delegate mechanism, rather than a simpler try/catch block, allows you to determine the error, handle the situation, and continue processing if you like. The parameter supplies a property: set this property to true to indicate that you have handled the error and wish to continue processing; set the property to false to indicate that you wish to halt processing. Be aware that setting the property to false causes the code that triggered the problem to throw an exception.

  The parameter allows you to specify an array of instances, indicating the order of the tables corresponding to each result set loaded from the reader. The method fills each supplied instance with data from a single result set from the source data reader. After each result set, the method moves on to the next result set within the reader, until there are no more result sets.

  The name resolution scheme for this method is the same as that followed by the method of the class.

  Fills a with values from a data source using the supplied , using an array of instances to supply the schema and namespace information.

  An that provides one or more result sets. A value from the enumeration that indicates how rows already in the instances within the will be combined with incoming rows that share the same primary key. A delegate to call when an error occurs while loading data. An array of instances, from which the method retrieves name and namespace information.
- Property
  System.Globalization.CultureInfo A that contains data about the user's machine locale. The default is a null reference.

  The property specifies the locale for which sorting applies.

  By default, setting the for a also sets the for each object in that DataSet to the same value.

  In columns that contain expressions, the is used. The is ignored.

  Gets or sets the locale information used to compare strings within the table.

  1.0.5000.0
  2.0.0.0
- Method
  System.Void ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of a merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges an array of objects into the current .

  The array of DataRow objects to be merged into the DataSet. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges a specified and its schema into the current DataSet.

  The DataSet whose data and schema will be merged. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges a specified and its schema into the current .

  The whose data and schema will be merged. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges a specified and its schema into the current DataSet, preserving or discarding any changes in this DataSet according to the given argument.

  The DataSet whose data and schema will be merged. true to preserve changes in the current DataSet; otherwise false. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` `` ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  To facilitate explanation of the method, we use "target" to signify the current , and "source" to name the second (parameter) . The target is so named because it is the object upon which an action (the merge) occurs. The second is called a "source" because the information it contains does not change, but instead is merged into the current .

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges an array of objects into the current , preserving or discarding changes in the DataSet and handling an incompatible schema according to the given arguments.

  The array of objects to be merged into the DataSet. true to preserve changes in the DataSet; otherwise false. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` `` ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  In a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  To facilitate explanation of the method, we use "target" to signify the current , and "source" to name the second (parameter) . The target is so named because it is the object upon which an action (the merge) occurs. The second is called a "source" because the information it contains does not change, but instead is merged into the current .

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges a specified and its schema with the current DataSet, preserving or discarding changes in the current DataSet and handling an incompatible schema according to the given arguments.

  The DataSet whose data and schema will be merged. true to preserve changes in the current DataSet; otherwise false. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` `` ``

  The method is used to merge two objects that have largely similar schemas. A merge is typically used on a client application to incorporate the latest changes from a data source into an existing . This allows the client application to have a refreshed with the latest data from the data source.

  The method is typically called at the end of a series of procedures that involve validating changes, reconciling errors, updating the data source with the changes, and finally refreshing the existing .

  iOn a client application, it is common to have a single button that the user can click that gathers the changed data and validates it before sending it back to a middle-tier component. In this scenario, the method is first invoked. That method returns a second optimized for validating and merging. This second object contains only the and objects that were changed, resulting in a subset of the original . This subset is generally smaller, and thus more efficiently passed back to a middle-tier component. The middle-tier component then updates the original data source with the changes through stored procedures. The middle tier can then send back either a new that includes original data and the latest data from the data source (by running the original query again), or it can send back the subset with any changes that have been made to it from the data source. (For example, if the data source automatically creates unique primary key values, these values can be propagated back to the client application.) In either case, the returned can be merged back into the client application's original with the method.

  When the method is called, the schemas of the two objects are compared because it is possible that the schemas may have been changed. For example, in a business-to-business scenario, new columns may have been added to an XML schema by an automated process. If the source contains schema elements (added objects) that are missing in the target, the schema elements can be added to the target by setting the argument to MissingSchemaAction.Add. In that case, the merged contains the added schema and data.

  After merging schemas, the data is merged.

  When merging a new source into the target, any source rows with a value of Unchanged, Modified, or Deleted are matched to target rows with the same primary key values. Source rows with a DataRowState value of Added are matched to new target rows with the same primary key values as the new source rows.

  During a merge, constraints are disabled. If any constraints cannot be enabled at the end of merge, a is generated and the merged data is retained while the constraints are disabled. In this case, the property is set to false, and all rows that are invalid are marked in error. The errors must be resolved before attempting to reset the property to true.

  Merges a specified and its schema into the current DataSet, preserving or discarding changes in the DataSet and handling an incompatible schema according to the given arguments.

  The DataTable whose data and schema will be merged. One of the values. true to preserve changes in the DataSet; otherwise false. 1.0.5000.0 2.0.0.0
- Event
  System.Data.MergeFailedEventHandler

  For more information about handling events, see [<topic://cpconEventsOverview>].

  Occurs when a target and source have the same primary key value, and is set to true.

  1.0.5000.0
  2.0.0.0
- Property
  System.String The namespace of the DataSet.

  The property is used when reading and writing an XML document into the using the , , , or methods.

  The namespace of an XML document is used to scope XML attributes and elements when read into a . For example, if a contains a schema that was read from a document with the namespace "myCompany," and an attempt is made to read data only from a document with a different namespace, any data that does not correspond to the existing schema is ignored.

  Gets or sets the namespace of the .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DefaultValue("")
- Method
  1.0.5000.0
  2.0.0.0
  System.Void ``

  Raising an event invokes the event handler through a delegate. For an overview, see Raising an Event.

  Raises the event.

  A that contains the event data.
- Method
  System.Void ``

  This method should be overridden by subclasses to restrict tables being removed

  Occurs when a object is removed from a .

  The being removed. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  This method can be overridden by subclasses to restrict tables from being removed.

  Occurs when a is removed from a .

  The being removed. 1.0.5000.0 2.0.0.0
- Property
  System.String The XML prefix for the DataSet namespace.

  The property is used throughout an XML document to identify elements which belong to the namespace of the object (as set by the property).

  Gets or sets an XML prefix that aliases the namespace of the .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DefaultValue("")
- Method
  1.0.5000.0
  2.0.0.0
  System.Void `` To be added.

  Sends a notification that the specified property is about to change.

  The name of the property that is about to change.
- Method
  System.Data.XmlReadMode ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema, as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified .

  The used to read the data.

  An object that derives from . 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  Classes that inherit from the class include the and classes.

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified .

  The used to read the data.

  The TextReader from which to read the schema and data. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes a targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified file.

  The XmlReadMode used to read the data.

  The filename (including the path) from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes a targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  inherits from .

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified .

  The XmlReadMode used to read the data.

  The from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode `` ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  The same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  When you use and you set to Diffgram, the content of the target DataSet and the original DataSet may differ because of how the diffgram is generated and processed. For more information on diffgrams, see DiffGrams.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified and .

  The XmlReadMode used to read the data.

  The from which to read. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode `` ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified and .

  The XmlReadMode used to read the data.

  The from which to read. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode `` ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes a targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified file and .

  The XmlReadMode used to read the data.

  The filename (including the path) from which to read. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Data.XmlReadMode `` ``

  The method provides a way to read either data only, or both data and schema into a from an XML document, whereas the method reads only the schema. To read both data and schema, use one of the ReadXML overloads that includes the parameter, and set its value to ReadSchema.

  Note that the same is true for the and methods, respectively. To write XML data, or both schema and data from the DataSet, use the WriteXml method. To write just the schema, use the WriteXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  If an in-line schema is specified, the in-line schema is used to extend the existing relational structure prior to loading the data. If there are any conflicts (for example, the same column in the same table defined with different data types) an exception is raised.

  If no in-line schema is specified, the relational structure is extended through inference, as necessary, according to the structure of the XML document. If the schema cannot be extended through inference in order to expose all data, an exception is raised.

  The DataSet does not associate an XML element with its corresponding DataColumn or DataTable when legal XML characters like ("_") are escaped in the serialized XML. The DataSet itself only escapes illegal XML characters in XML element names and hence can only consume the same. When legal characters in XML element name are escaped, the element is ignored while processing.

  If the XML Schema for a includes a targetNamespace, data may not be read, and you may encounter exceptions when calling to load the with XML that contains elements with no qualifying namespace. To read unqualified elements, set elementFormDefault equal to "qualified" in your XML Schema as the following example demonstrates.

  `<xsd:schema id="MyDataSet" elementFormDefault="qualified" targetNamespace="http://www.tempuri.org/MyDataSet.xsd" xmlns="http://www.tempuri.org/MyDataSet.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> </xsd:schema>`

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with by specifying XmlReadMode.ReadSchema. This exception does not occur if you are using .NET Framework version 1.0.

  Reads XML schema and data into the using the specified and .

  The XmlReadMode used to read the data.

  The from which to read. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to create the schema for a . The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  Data corruption can occur if the msdata:DataType and the xs:type types do not match. No exception will be thrown.

  The method is generally invoked before invoking the method which is used to fill the .

  Classes that derive from the class include , , , and .

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is be thrown when you attempt to read the schema into the with . This exception does not occur if you are using .NET Framework version 1.0.

  Reads the XML schema from the specified into the .

  The from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to create the schema for a . The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  Data corruption can occur if the msdata:DataType and the xs:type types do not match. No exception will be thrown.

  The method is generally invoked before invoking the method which is used to fill the .

  Classes that inherit from the class include the and classes.

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is be thrown when you attempt to read the schema into the with . This exception does not occur if you are using .NET Framework version 1.0.

  Reads the XML schema from the specified into the .

  The from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to create the schema for a . The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  Data corruption can occur if the msdata:DataType and the xs:type types do not match. No exception will be thrown.

  The method is generally invoked before invoking the method which is used to fill the .

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is thrown when you attempt to read the schema into the with . This exception does not occur if you are using .NET Framework version 1.0.

  Reads the XML schema from the specified file into the .

  The file name (including the path) from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to create the schema for a . The schema includes table, relation, and constraint definitions.

  The XML schema is written using the XSD standard.

  Data corruption can occur if the msdata:DataType and the xs:type types do not match. No exception will be thrown.

  The method is generally invoked before invoking the method which is used to fill the .

  The class is abstract. A class that inherits from the XmlReader is the class.

  If the schema for your contains elements of the same name, but different type, in the same namespace, an exception is be thrown when you attempt to read the schema into the with . This exception does not occur if you are using .NET Framework version 1.0.

  Reads the XML schema from the specified into the .

  The from which to read. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` To be added

  Ignores attributes and returns an empty DataSet.

  The specified XML reader. 1.0.5000.0 2.0.0.0
- Method
  System.Void

  Invoke the to call the method on all objects contained by the .

  objects contained by the can each be set into edit mode by invoking the method. After invoking the method, changes can be rejected by calling the on the to which the objects belong.

  When the method is called, any rows still in edit-mode cancel their edits. New rows are removed. Modified and deleted rows return back to their original state (DataRowState.Unchanged).

  AcceptChanges and RejectChanges only apply to related changes (that is, Add, Remove, Delete, and Modify). They are not applicable to schema or structural changes.

  Rolls back all the changes made to the since it was created, or since the last time was called.

  1.0.5000.0
  2.0.0.0
- Property
  System.Data.DataRelationCollection A that contains a collection of objects, a null value if no DataRelation objects exist.

  Get the collection of relations that link tables and allow navigation from parent tables to child tables.

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Content)
- Property
  2.0.0.0
  System.ComponentModel.DefaultValue(System.Data.SerializationFormat.Xml)
  System.Data.SerializationFormat To be added. To be added.

  Gets or sets a for the used during remoting.

- Method
  System.Void Resets the object to its original state, that is, removes all the constraints, clears all the tables and deletes all the relations.

  Clears all tables and removes all relations, foreign constraints, and tables from the . Subclasses should override to restore a to its original state.

  1.0.5000.0
  2.0.0.0
- Property
  2.0.0.0
  System.ComponentModel.Browsable(false)
  System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Hidden)
  System.Data.SchemaSerializationMode To be added.

  A serializes its schema and instance data by default in Web services and remoting scenarios. Setting the property of a typed DataSet to causes schema information to be excluded from the serialization payload.

  is supported only for a typed DataSet. For an un-typed DataSet this property can only be set to .

  should only be used in cases where the schema information of the underlying typed DataTables, DataRelations and Constraints has not been modified. If modifications have occurred, complete schema information should be serialized with .

  is supported in version 2.0 of the .NET Framework or later.

  When is set, only the top level runtime properties present on the are serialized. In addition, they are serialized only if they happen to be different from the default values. None of the Tables, Relations or Constraints are serialized. The serialized runtime properties include , , , , , and . These properties are serialized to make sure that overall runtime data integrity is preserved.

  Gets or sets a for a .

- Method
  System.Boolean

  You typically use this method if you are either creating a designer for the , or creating your own control incorporating the .

  Gets a value indicating whether property should be persisted.

  true if the property value has been changed from its default; otherwise false.

  1.0.5000.0
  2.0.0.0
- Method
  System.Boolean

  You typically use this method only if you are either creating a designer for the , or creating your own control incorporating the .

  Gets a value indicating whether property should be persisted.

  true if the property value has been changed from its default; otherwise false.

  1.0.5000.0
  2.0.0.0
- Property
  System.ComponentModel.ISite An for the DataSet.

  Sites bind a to a and enable communication between them, as well as provide a way for the container to manage its components.

  Gets or sets an for the .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Hidden)
  System.ComponentModel.Browsable(false)
- Property
  1.0.5000.0
  2.0.0.0
  System.Boolean To be added.

  This member is an explicit interface member implementation. It can be used only when the instance is cast to an interface.

  For a description of this member, see .

- Method
  1.0.5000.0
  2.0.0.0
  System.Collections.IList

  This member is an explicit interface member implementation. It can be used only when the instance is cast to an interface.

  For a description of this member, see .

  For a description of this member, see .

- Method
  1.0.5000.0
  System.Void `` `` To be added.

  Populates a serialization information object with the data needed to serialize the .

  The to populate with data. The destination (see ) for this serialization.
- Method
  1.0.5000.0
  2.0.0.0
  System.Xml.Schema.XmlSchema

  This member is an explicit interface member implementation. It can be used only when the instance is cast to an interface.

  For a description of this member, see .

  For a description of this member, see .

- Method
  1.0.5000.0
  2.0.0.0
  System.Void ``

  This member is an explicit interface member implementation. It can be used only when the instance is cast to an interface.

  For a description of this member, see .

  A .
- Method
  1.0.5000.0
  2.0.0.0
  System.Void ``

  This member is an explicit interface member implementation. It can be used only when the instance is cast to an interface.

  For a description of this member, see .

  A .
- Property
  System.Data.DataTableCollection The contained by this DataSet; otherwise a value if no objects exist.

  To add tables to the collection, use method of the . To remove tables, use the method.

  Gets the collection of tables contained in the .

  1.0.5000.0
  2.0.0.0
  System.ComponentModel.DesignerSerializationVisibility(System.ComponentModel.DesignerSerializationVisibility.Content)
- Method
  System.Void ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, use one of the overloads that includes the parameter, and set its value to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data for the using the specified .

  A object used to write to a file. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, use one of the overloads that includes the parameter, and set its value to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data for the using the specified .

  The object with which to write. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, use one of the overloads that includes the parameter, and set its value to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data for the to the specified file.

  The file name (including the path) to which to write. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, use one of the overloads that includes the parameter, and set its value to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data for the to the specified .

  The with which to write. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, set the parameter to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data, and optionally the schema, for the using the specified and . To write the schema, set the value for the parameter to WriteSchema.

  A object used to write to a file. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, set the parameter to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data, and optionally the schema, for the using the specified and . To write the schema, set the value for the parameter to WriteSchema.

  A object used to write the document. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, set the parameter to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data, and optionally the schema, for the to the specified file using the specified . To write the schema, set the value for the parameter to WriteSchema.

  The file name (including the path) to which to write. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void `` ``

  The WriteXml method provides a way to write either data only, or both data and schema from a into an XML document, whereas the method writes only the schema. To write both data and schema, set the parameter to WriteSchema.

  Note that the same is true for the and methods, respectively. To read XML data, or both schema and data into the DataSet, use the ReadXml method. To read just the schema, use the ReadXmlSchema method.

  An will be thrown if a column type in the DataRow being read from or written to implements and does not implement .

  Writes the current data, and optionally the schema, for the using the specified and . To write the schema, set the value for the parameter to WriteSchema.

  The with which to write. One of the values. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to write the schema for a to an XML document. The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  To write the data to an XML document, use the method.

  Classes that derive from the class include , , , and .

  Writes the structure as an XML schema to the specified object.

  A object used to write to a file. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to write the schema for a to an XML document. The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  To write the data to an XML document, use the method.

  Classes the derive from the class include the , , , , and .

  Writes the structure as an XML schema to the specified object.

  The object with which to write. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to write the schema for a to an XML document. The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  To write the data to an XML document, use the method.

  Writes the structure as an XML schema to a file.

  The file name (including the path) to which to write. 1.0.5000.0 2.0.0.0
- Method
  System.Void ``

  Use the method to write the schema for a to an XML document. The schema includes table, relation, and constraint definitions. To write a schema to an XML document, use the method.

  The XML schema is written using the XSD standard.

  To write the data to an XML document, use the method.

  One class that inherits from the class is the class.

  Writes the structure as an XML schema to an object.

  The to write to. 1.0.5000.0 2.0.0.0