LLBLGen Pro vs Entity Framework

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.

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

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).

Choice between Database first or Model first approach.

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

Supports most popular databases.

Better than the chaotic and confusing NHibernate documentation.

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

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.

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

Object model is non-intrusive and consistent.