When comparing Entity Framework vs DevExpress XPO, the Slant community recommends DevExpress XPO for most people. In the question“What are the best ORMs for C#?” DevExpress XPO is ranked 1st while Entity Framework is ranked 3rd. The most important reason people chose DevExpress XPO is:
Most popular databases are supported, including MS Access, MS SQL Server, PostgreSQL, MySQL, SQLite and Oracle.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Migrations API
List all versions of a schema, apply one or go back to a previous version.
Pro Database support
Supports most popular databases.
Pro Documentation
Better than the chaotic and confusing NHibernate documentation.
Pro Typesafe queries
Linq2Sql allows writing queries using the actual ORM types. This prevents issues when modifying the schema/entities.
Pro Avoids creation of inline SQL queries
No longer do you have to create/close SQL connections every time you want to interact with the database. You also don't have to maintain a database reader to handle the results retrieved from the database; all of this functionality is easily handled through LINQ queries and Entity Framework.
Pro Database agnostic
You can quite easily migrate from using one DB technology to another.
Pro Non intrusive object model
Object model is non-intrusive and consistent.
Pro Database support
Most popular databases are supported, including MS Access, MS SQL Server, PostgreSQL, MySQL, SQLite and Oracle.
Pro .NET Core support
Cons
Con Complicated
For simple data storage scenarios, EF may be unnecessarily complicated to learn.
Con Performance
Micro-ORMs have better performance.
Con Disconnected objects
Every classes have to inherits from an ancestor object, very hard disconnect objects support.
Con No Migrations support
Doesn't have the ability to apply schema migration steps based on the schema version found in the database at startup.