XPO Classes Structure
- 2 minutes to read
Use the following links to access reference information about the most important classes in XPO.
Stores persistent objects in memory. Intended for testing environment. This data store is useful for in-memory object manipulations. Not designed for large data sets.
Built-in connection providers implementing data-aware operations for the MS Access, MS SQL Server, and MS SQL Azure databases.
A data source providing persistent objects for data-aware web controls.
The main classes that provide functionality for cached data stores.
The main classes allowing you to transfer data over the wire in your distributed applications via WCF services.
Stores global settings such as a connection string or a shared data access layer, and simplifies the implementation of multi-session applications.
A base class for persistent objects providing basic functionality. This class is useful when mapping your persistent objects to existing databases.
The main built-in attributes allowing you to properly map your persistent objects to database objects.
A Unit of Work allowing you to manage persistent object modifications using semi-automatically maintained transactions.
A nested unit of work allowing you to manage persistent object modifications within the scope of its parent unit of work.
A collection of persistent objects and its generic type counterpart.
The data source that displays data from result sets.
The view that stores data retrieved from persistent objects.
A query that allows the construction of LINQ queries for persistent objects.