xaf-xpo-models

Create standardized XPO persistent object models for DevExpress XAF projects.

6|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/kashiash/xaf-skills --skill xaf-xpo-models
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xaf-xpo-models
Source: https://github.com/kashiash/xaf-skills/tree/main/xaf-xpo-models
Command: npx skills add https://github.com/kashiash/xaf-skills --skill xaf-xpo-models

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XAF developers often struggle to design consistent XPO persistent object models and their relationships. This guide provides base classes, attributes, and relation patterns to standardize object modeling and reduce boilerplate.

Core Features & Use Cases

  • XPObject, XPBaseObject, XPCustomObject, and BaseObject base classes with recommended usage
  • One-to-many, many-to-many, and one-to-one relations with proper associations
  • PersistentAlias, session access patterns, and common XPO pitfalls to avoid

Quick Start

Define a minimal XPO model ready to extend in your XAF application.

Frequently Asked Questions about xaf-xpo-models

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define XPO persistent object models for a DevExpress XAF application?

To define XPO persistent object models for DevExpress XAF, you use base classes like XPObject or BaseObject, apply key attributes, and implement relation patterns to standardize object modeling and reduce boilerplate code.

What is the difference between XPObject, XPBaseObject, XPCustomObject, and BaseObject in XPO?

XPObject, XPBaseObject, XPCustomObject, and BaseObject are XPO base classes with distinct recommended usages. Choosing the right base class dictates key attribute handling and session access patterns for your persistent object models.

How do I configure one-to-many and many-to-many relations in XPO?

Configuring one-to-many and many-to-many relations in XPO requires applying proper associations to your persistent object models. Standardizing these relation patterns ensures data integrity and prevents common XPO pitfalls.

What are common XPO pitfalls when accessing sessions and using PersistentAlias?

Common XPO pitfalls involving session access patterns and PersistentAlias often lead to runtime errors. Applying standardized base class definitions and attribute usage helps avoid these frequent data layer mistakes.

Can I use XPO model definitions across different UI platforms in XAF?

Yes, XPO model definitions apply across typical UI platforms supported by DevExpress XAF. By standardizing base classes and relation patterns, your persistent objects remain platform-agnostic within the application framework.