For new projects, do you prefer EF, ADO, Dapper or something else?

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • SonarQube - Static code analysis for 29 languages.
  • InfluxDB - Access the most powerful time series database as a service
  • SaaSHub - Software Alternatives and Reviews
  • SqlMarshal

    Generates data access using stored procedures

    After writing SQL, I prefer to interface with dotnet code via auto-generated types. This gives type safety compared to Dapper and manually generated ADO. I just posted an issue giving some libraries which do this here:

  • NReco.Data

    Fast DB-independent DAL for .NET Core: abstract queries, SQL commands builder, schema-less data access, POCO mapping (micro-ORM). (by nreco)

    We use in our products, similar to Dapper but with built-in SQL generation for CRUD-queries (it is very easy to compose filters in run-time) + hand-written SQL may be concentrated in one place (app-level 'dataviews').

  • SonarQube

    Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts