Skip to main content
BuyLog In
XPO (.NET ORM Library)
Search in…
Docs > Create a Data Model > XPO Classes Comparison
A newer version of this page is available. .
All docs
V21.1
.NET Framework 4.5.2+
eXpress Persistent Objects
.NET Core 3.0+ and .NET Standard 2.0 Support
Getting Started
Product Information
Connect to a Data Store
Create a Data Model
Create a Persistent Object
Relationships Between Objects
Basics of Creating Persistent Objects for Existing Data Tables
Generating Persistent Objects for Existing Data Tables
Add Persistence to an Existing Hierarchy: Change the Base Inheritance
Add Persistence to an Existing Hierarchy: Session-less Persistent Objects
Inheritance Mapping
Work with Structures
Value Converters
Property Descriptors
XPO Classes Comparison
Upcasting
When and Why XPO Extends the Database Schema
Built-In Attributes
Create-Read-Update-Delete (CRUD)
Query and Shape Data
Best Practices and Troubleshooting
Design-Time Features
Examples
Member Tables
API Reference
Download CHM

XPO Classes Comparison

You can derive persistent objects from the PersistentBase, XPBaseObject, XPObject, XPLiteObject and XPCustomObject classes.

XPOClassHierarchy

When objects are derived from a class, XPO features are automatically enabled for this object. For example, the OptimisticLockingAttribute is automatically applied to objects derived from the PersistentBase, XPBaseObject, XPCustomObject or XPObject class. This enables the optimistic locking feature. However, this feature is disabled when objects are derived from the XPLiteObject class.

The following table illustrates the differences between XPO classes:

Class Name Deferred Deletion Optimistic Locking Built-in OID key
PersistentBase No Yes No
XPBaseObject No Yes No
XPLiteObject No No No
XPCustomObject Yes Yes No
XPObject Yes Yes Yes

Tip

We recommend that you use the PersistentBase class as the base class for persistent classes in WPF applications. For additional information, see XPO Best Practices in WPF applications.