Traditional Data Binding Methods
- 2 minutes to read
DevExpress data-aware .NET WinForms controls (XtraGrid, XtraPivotGrid, XtraTreeList, XtraScheduler, XtraChart and XtraVerticalGrid) can be bound to various data sources. This topic lists typical data sources to which controls can be bound. For data binding specifics that are related to specific controls, refer to the corresponding product's documentation.
Typical data sources supported by DevExpress data-aware .NET WinForms controls include:
Simplifies binding controls to data by providing currency management, change notification, and other services between Windows Forms controls and data sources. The BindingSource component can act as a strongly-typed data source.
Represents a complete set of data that includes tables that contain, order, and constrain data, as well as the relationships between the tables. A DataSet can read and write data and schema as XML documents. See DataSets, DataTables, and DataViews for more information.
Represents one table of in-memory data.
Provides a generic collection that supports data binding.
Represents a strongly typed list of objects that can be accessed by index. Provides methods to search, sort, and manipulate lists.
Provides functionality to discover the schema for a bindable list where the properties available for binding differ from the public properties of the object to bind to.
Provides features that support both complex and simple binding scenarios.
Represents a non-generic collection of objects that can be individually accessed by the index.
Any array of objects.
Data-aware controls usually provide the DataSource and DataMember properties that let you bind them to a data source. In most cases, a control can be bound to a data source using the DataSource property alone (the DataMember property is left set to an empty string).
A data source (e.g., a DataSet object) may contain several lists, tables or data relationships. To bind the control in this case, set the control's DataSource property to the aggregated data source and set its DataMember property to the name that identifies the desired table/list/data relationship.