53
User
Recs.
Recs.
18
Updates
Last
Updated
Updated
Activity
28 Options
Specs
Specs are quantitative aspects of the option such as the price
Pros
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.
Know any positive aspects of this option?
Cons
Recommendations
Entity Framework
Recommended a year ago
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 percen...
Pro
Database supportPro
Migrations APIPro
DocumentationPro
Typesafe queriesPro
Avoids creation of inline SQL queriesEntity Framework
Recommended 2 years ago
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'...
Pro
Database supportPro
DocumentationPro
Database agnosticPro
Typesafe queriesPro
Non intrusive object modelPro
Avoids creation of inline SQL queriesEntity Framework
Recommended 3 years ago
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 difficu...
Pro
Migrations APIPro
DocumentationPro
Non intrusive object modelEntity Framework
Recommended 4 years ago
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.
Pro
Database supportEntity Framework
Recommended 4 years ago
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 s...
Pro
Database support