What are the best ORMs for C#?

Question

DevelopmentDatabases.NetORMs

What are the best ORMs for C#?

28

Options
Considered

552

User
Recs.

Feb 6, 2024

Last
Updated

26 Options Considered

Best ORMs for C#	Price	Last Updated
85 DevExpress XPO	Free / paid	Jan 14, 2024
-- Dapper	Free	Feb 6, 2024
-- Entity Framework	Free	Feb 1, 2024
-- DbConnector	Free	Aug 23, 2023
-- LINQ to SQL	Free	Nov 27, 2023

See Full List

DbConnector

EntitySpaces

Built By the Slant team

Find the best product instantly.

4.7 star rating

Try it now - it's free

score 154 · Answer 1

DevExpress XPO

Top Pro

Database support

Most popular databases are supported, including MS Access, MS SQL Server, PostgreSQL, MySQL, SQLite and Oracle. See More

Top Con

Disconnected objects

Every classes have to inherits from an ancestor object, very hard disconnect objects support. See More

ReasonableAnteros's Experience

Best ••• tool you'll ever ••• find. ••• entity framework which is a piece of ••• See More

Top Pro

.NET Core support

Top 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. See More

KindTethys's Experience

You can hardly call a tool free when it don't ••• work right and a support plan is thousands of dollars. Ranks right up there with the other DevExpress crap. See More

SuccinctKishar's Experience

Support for lots of databases. Very efficient and fast. Using in existing XAF and non-XAF applications with very large databases. See More

See All

score 74 · Answer 2

Dapper

Top Pro

Very efficient and quick

Top Con

Not even slightly typesafe

If you make a typo in the SQL your CI server is not going to catch it, you'll have to hope it's caught during automated UI or functional testing. See More

NonchalantGenann's Experience

Fast, flexible, free See More

Top Pro

No need to roll your own conversion layer for the DataReader

Top Con

A pain to maintain

You've got a bunch of inline SQL statements that do various queries that have no strong ties to the DB architecture. This can quite easily lead to queries that get "left behind" when the underlying DB structure changes, which, again, you will not see at build time. See More

PositiveAlecto's Experience

This is a DBA's worse nightmare. SQL strings scattered about the software, how do you expect me to optimize queries. This is a silly tool that does more harm than good. See More

Top Pro

Similar performance to a raw SqlCommand with DataReader and parsing

Top Con

It doesn't generate a class model or queries for you

ImaginativeAhPeku's Experience

Has advantages of ORM but lets me use raw SQL See More

Top Pro

Makes it trivially easy to turn results into objects

Top Con

It doesn't track objects and their changes so you can just call SubmitChanges()

PopularHozanek's Experience

StackOverflow and other websites of stackexchange are using this. Dapper extend the IDbConnection by providing useful extension methods to query your database. See More

Top Pro

Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)

DeliberateIlmatar's Experience

You have SQL buried in string literals, safely out of reach of validation, profiling or testing so it's a crap shoot. Maintenance disaster stay away from this. See More

Top Pro

Makes it trivially easy to correctly parameterize queries

OpinionatedWanamangura's Experience

As a DBA, this is a terrible approach. Nothing worse than having to sift through code to track down non-performant queries to remove bottle necks. See More

See All

score 53 · Answer 3

Entity Framework

Top Pro

Migrations API

List all versions of a schema, apply one or go back to a previous version. See More

Top Con

Complicated

For simple data storage scenarios, EF may be unnecessarily complicated to learn. See More

AssertiveElegua's Experience

I've used this on two projects that converted existing .Net Framework apps using ADO.Net to .Net Core with EF Core. A bit of a learning curve but in the end glad we made the switch. Saved a ton of time by eliminating all unit tests for the data service tier. EF Core 6 is very fast, within a few percentage points of ADO.Net and stored procedures. Using SQL Server as our RDBMS, but also have good experiences with MySQL and PostgreSQL. Using Azure Devops Server (onprem) for release pipeline; each stage has a step to run Migrations to keep schemas in sync for all instances (dev, test, prod). See More

Top Pro

Database support

Supports most popular databases. See More

Top Con

Performance

Micro-ORMs have better performance. See More

WittyMara's Experience

I have been using Entity Framework for the past several years and I love the way it seamlessly integrates into my applications within Visual Studio. This is to be expected since Entity Framework was developed by Microsoft. In the past, I have also used NHibernate and a few other ORM's; however, I don't feel any of them integrated into my applications as easily as Entity Framework. See More

Top Pro

Documentation

Better than the chaotic and confusing NHibernate documentation. See More

DetailedEnnugi's Experience

Poor annotation system, fussy migration before updating database structure, annoying concurrency exception when doing asynchronous operations. See More

Top Pro

Typesafe queries

Linq2Sql allows writing queries using the actual ORM types. This prevents issues when modifying the schema/entities. See More

WonderfulTonatiuh's Experience

Having practiced both XPO and EFCore, I can say that EFCore is much easier to use, at least for people who know what a DBMS is. Although XPO is attractive and easy to use with its built-in designer, all XPO objects are linked to an ancestor, which makes working with disconnected objects particularly difficult. EFCore adapts to any type of class of entities, no matter how rich, of a quasi-transparent material (yes, it is possible), and will thus easily satisfy the needs of both schools that are facing each other: those that incorporate their persistence logic in the business layer, and those that separate it completely. In addition, EFCore has a migration model that is particularly adapted and well thought out. On the other hand, the generation of SQL XPO is particularly powerful, that of EFCore seems very slightly behind. But it is only a question of query formulation. Moreover, XPO hosts more DBMS. In spite of this, my preference goes anyway to EFCore: its object model is elegant, coherent and more important : non intrusive. The more I use it, the more I have the impression that Microsoft has thought of everything. The main overall impression I feel between XPO and EFCore is that EFCore integrates with my applications, whereas I feel like I have to integrate my applications with XPO. See More

Top 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. See More

PerceptiveKhumban's Experience

Excellent choice for both junior and senior developers. Avoids having to write boiler plate code for common tasks (i.e. ORM) while leaving enough room for SQL-Specialists to write and execute supersophisticated highperformance queries and stored procedures. See More

Top Pro

Database agnostic

You can quite easily migrate from using one DB technology to another. See More

IndependentAengus's Experience

Very Slow and laking auto migrations. See More

Top Pro

Non intrusive object model

Object model is non-intrusive and consistent. See More

IntellectualTailtiu's Experience

very good ORM fetch navigated entity as well work as plain linq See More

BrilliantAbundantia's Experience

Might be good for Jr Developers, but not much more. Why would a SQL Developer want to query the database with LINQ, maybe MS should rethink the approach. See More

HealthyPeitharchia's Experience

We have a very large database, 1000's of tables millions of records. Just not a tool that holds up for us. See More

DiplomaticMunsin's Experience

EF Core is very flexible for handling disconnected objects. Much more than XPO which requires objects to remain connected to the equivalent of a DbContext. So much so that one might be tempted to use the entities everywhere in one's application, not just in the persistence layer, which doesn't seem such a bad idea in most scenarios after all, because the navigation properties are so flexible. The schema migration tools are extraordinarily simple and well thought out. See More

WonderfulOmoikane's Experience

Microsoft should spend more resources on the actual tool than on evangelists over hyping poor products. This tool tries to be the end all be all tool for data tier, but just don't live up to the hype. See More

InsightfulVeles's Experience

After using this tool for a short while, I've come to the conclusion that it is strictly for beginners. If you are serious about data and it is vital to your organization, this is not the tool you should be using. See More

OptimisticPorphyrion's Experience

Used EF for 3 months, write code, deploy code, cross fingers. See More

EncouragingPistis's Experience

Spent more time sifting through stack overflow trying to resolve problems than we did writing code. Microsoft should be ashamed to advocate a tool that is so convoluted. See More

ProductiveBeaivi's Experience

In the beginning it saved us some time, but in the long run it's become a pain in the ass See More

RobustTskarishdida's Experience

Maintenance disaster See More

ExuberantLoviatar's Experience

Slow, clunky, prone to all sorts of problems See More

AmiableSuurToll's Experience

Development faster and easy for begginers :) See More

See All

score 13 · Answer 4

LINQ to SQL

Top Pro

Free

Top Con

SQL Server oriented

To use other databases than Microsoft SQL Server, 3rd party software is needed. See More

PioneeringArke's Experience

Very easy to start with, fast, not very memory-hungry and effective for most scenarios. Nice and functional graphic designer. Property changed notifications are included, contrary to more recent ORMs such as EF 6 and EF Core. See More

RickZeeland's Experience

LINQ to SQL allows the direct 1-1 mapping of a Microsoft SQL Server database to .NET classes, and querying of the resulting objects using LINQ. See More

See All

score 11 · Answer 5

NHibernate

Top Con

Chaotic documentation

score 13 · Answer 6

ServiceStack.OrmLite

score 20 · Answer 7

Venflow

Top Pro

Fast

Top Con

Only PostgreSQL

Only PostgreSQL is supported at the moment. See More

DignifiedEunostus's Experience

Excelent See More

Top Pro

Effective

Venflow has some very innovative solutions that reduce memory usage See More

ImaginativeSelene's Experience

It was very fast and a good documentation See More

Top Pro

Change tracking

Simple change-tracking for update operations. See More

See All

score 17 · Answer 8

LLBLGen Pro

Top Pro

Async API

The runtime framework offers a full Async API for retrieval of data and object persistence, using .NET async/await statements to build truly asynchronous applications. Usable in Linq, QuerySpec and the Low-Level API. See More

Top Con

Not free

No free plan available. See More

FerventVellamo's Experience

The ORM is stable and matured. It integrates very well with different third-party interface components. See More

Top Pro

Multi framework support

Besides the LLBLGen Pro Runtime Framework, it supports Entity Framework Core / Full, NHibernate and Linq to Sql. See More

RickZeeland's Experience

LLBLGen Pro can generate a complete data-access tier and business objects tier (multiple target frameworks, C# or VB.NET*), it features powerful O/R mapping technology and has a flexible task-based code generator. See More

Top Pro

Fast and powerful

After 10 years using it, you just work with your C# objects. Never had to go for work arounds. Never complained with performance (some thousand concurrent connections). See More

Top Pro

Database first / Model first

Choice between Database first or Model first approach. See More

See All

score 10 · Answer 9

SQL+ .NET

Top Pro

Performance

Because SQL+ .NET is a build time ORM, there is no trans piling or dynamic mapping at run time. Your generated services will run as efficient as possible. See More

Top Con

Not an entry level programmers tool

This tool is best suited to more experience developers who have knowledge of SQL, and at least some exposure to C# without those you would probably find yourself somewhat challenged. See More

Top Pro

Productivity

Write your SQL, add a few comments (Semantic Tags) and generate your service. For developers who have invested time in learning SQL, there is simply no faster way to create data-services. See More

Top Pro

Maintainability

If you make a change to your SQL, simply regenerate your services and your code is synchronized. No need to chase down loose SQL text throughout your data tier. See More

Top Pro

Power

Because SQL+ is a SQL first ORM, you have the full power of the database at your disposal. Things that other tools find challenging or impossible to accomplish without add-ons or complicated workarounds, SQL+ gives you out of the box. Multiple result set queries, hierarchical or graph data, transient error management, scalar functions, table value functions, table value parameters, and the list goes on. See More

See All

score 6 · Answer 10

Insight.Database

score 16 · Answer 11

RepoDb

Top Pro

Fast

Top Con

Database Support

No Document Db Support See More

RickZeeland's Experience

Free and open source lightweight, efficient and very fast Hybrid ORM library for .NET. See More

Top Pro

Added Postgres and Mysql Support in Newer versions

See All

score 4 · Answer 12

SQLite-net

Top Pro

Single file

One file only, just add SQLite.cs to your project. See More

RickZeeland's Experience

SQLite-net open source and lightweight library providing easy SQLite 3 database storage for .NET, Mono, and Xamarin applications. See More

Top Pro

Easy integration

Easy integration with existing projects, runs on all the .NET platforms. See More

See All

score 2 · Answer 13

LINQ to DB

Top Pro

Free and open-source

RickZeeland's Experience

Supports popular databases like: MS Access, MS SQL Server, PostgreSQL, MariaDB, SQLite, Firebird, DB2, Informix and Oracle. See More

Top Pro

Database support

Most popular databases are supported, including MS Access, MS SQL Server, PostgreSQL, MariaDB, SQLite, Firebird, DB2, Informix and Oracle. See More

See All

score 4 · Answer 14

LinqConnect

Top Pro

Performance

Has features like compiled query cache or batch updates. See More

RickZeeland's Experience

LinqConnect is a fast and easy to use ORM solution, which can be used for free. It's developed closely to the Microsoft LINQ to SQL technology, and supports SQL Server, Oracle, MySQL, PostgreSQL, and SQLite. The model designer tool provides complete integration with Visual Studio - Entity Developer. See More

score 3 · Answer 15

MicroLite

Top Pro

Free

Top Con

Usage is not as widespread so fewer articles and tutorials

ResponsiveAtaguchu's Experience

Once properly set up, it is extremely convenient and works flawless. Interactions between your objects and database are automatic. Dapper was not nearly as convenient, although admittedly I just evaluated Dapper with a prototype. See More

Top Pro

Easy enough to set up

Top Pro

Extremely convenient

See All

score 3 · Answer 16

Massive

Top Con

No .NET Core support

score 5 · Answer 17

PetaPoco

Top Pro

Simple

Top Con

The simplicity means a lot more manual intervention

AffableMastoratia's Experience

Simple See More

Top Pro

Low level control

See All

score 8 · Answer 18

VITA ORM for .NET

Top Pro

Very easy and effective

RealisticManawydan's Experience

I Use it on my ERP and it is simply the best. See More

Top Pro

You can use it with every thing

SincereBeliMawr's Experience

Built a number of real-world apps See More

Top Pro

Actually usable

26 Options Considered

My Recommendation for DevExpress XPO

My Recommendation for DevExpress XPO

Database support

Disconnected objects

.NET Core support

No Migrations support

My Recommendation for Dapper

My Recommendation for Dapper

Very efficient and quick

Not even slightly typesafe

No need to roll your own conversion layer for the DataReader

A pain to maintain

Similar performance to a raw SqlCommand with DataReader and parsing

It doesn't generate a class model or queries for you

Makes it trivially easy to turn results into objects

It doesn't track objects and their changes so you can just call SubmitChanges()

Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)

Makes it trivially easy to correctly parameterize queries

My Recommendation for Entity Framework

My Recommendation for Entity Framework

Migrations API

Complicated

Database support

Performance

Documentation

Typesafe queries

Avoids creation of inline SQL queries

Database agnostic

Non intrusive object model

My Recommendation for DbConnector

My Recommendation for DbConnector

My Recommendation for LINQ to SQL

My Recommendation for LINQ to SQL

Free

SQL Server oriented

My Recommendation for NHibernate

My Recommendation for NHibernate

Chaotic documentation

My Recommendation for ServiceStack.OrmLite

My Recommendation for ServiceStack.OrmLite

My Recommendation for EntitySpaces

My Recommendation for EntitySpaces

My Recommendation for Venflow

My Recommendation for Venflow

Fast

Only PostgreSQL

Effective

Change tracking

My Recommendation for LLBLGen Pro

My Recommendation for LLBLGen Pro

Async API

Not free

Multi framework support

Fast and powerful

Database first / Model first

My Recommendation for SQL+ .NET

My Recommendation for SQL+ .NET

Performance

Not an entry level programmers tool

Productivity

Maintainability

Power

My Recommendation for Insight.Database

My Recommendation for Insight.Database

My Recommendation for RepoDb

My Recommendation for RepoDb

Fast

Database Support

Added Postgres and Mysql Support in Newer versions

My Recommendation for SQLite-net

My Recommendation for SQLite-net

Single file

Easy integration

My Recommendation for LINQ to DB

My Recommendation for LINQ to DB

Free and open-source

Database support

My Recommendation for LinqConnect

My Recommendation for LinqConnect