XPBaseCollection Class
An ancestor of the XPCollection class.
Namespace: DevExpress.Xpo
Assembly: DevExpress.Xpo.v23.2.dll
NuGet Packages: DevExpress.Win.PivotGrid, DevExpress.Win.TreeMap, DevExpress.Xpo
NuGet Package: DevExpress.Xpo
Declaration
public abstract class XPBaseCollection :
Component,
IBindingList,
ICollection,
IEnumerable,
IList,
ITypedList,
ISupportInitialize,
IXPClassInfoAndSessionProvider,
IXPClassInfoProvider,
IXPDictionaryProvider,
ISessionProvider,
IObjectLayerProvider,
IDataLayerProvider,
IObjectChange,
IFilteredXtraBindingList,
IFilteredDataSource,
IXPPrefetchableAssociationList,
IXPBulkLoadableCollectionpublic abstract class XPBaseCollection :
Component,
IBindingList,
IList,
ICollection,
IEnumerable,
ITypedList,
ISupportInitialize,
IXPClassInfoAndSessionProvider,
IXPClassInfoProvider,
IXPDictionaryProvider,
ISessionProvider,
IObjectLayerProvider,
IDataLayerProvider,
IObjectChange,
IFilteredXtraBindingList,
IFilteredDataSource,
IXPPrefetchableAssociationList,
IXPBulkLoadableCollectionRemarks
XPBaseCollection is an ancestor of the XPCollection class. Use XPCollection objects in your applications to represent collections of persistent objects. See the XPCollection concept for more information.
Note
The XPBaseCollection‘s implementation of the ITypedList interface limits the number of nesting levels in the object’s hierarchy to four levels at design time. This is done on purpose, because in some situations, Visual Studio attempts to retrieve the full hierarchy. This leads to Visual Studio hanging if the business model has self-referencing associations.
At runtime, there is no limitation for the nesting level, and you can bind controls to any property at runtime, even if it isn’t visible in the designer. Also, the end-user designer doesn’t inherit this problem, and the entire hierarchy will be retrieved.