Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
There is also such a thing as Nhibernate
as they say, it is similar to the Entity framework
If you generally have little idea of the principles of interaction with the database, then it is probably better to take the Entity Framework, but pay with performance. If you want to be 100% sure which scripts are sent to the database for execution - ADO.NET is your solution. According to Dapper, I saw a laudatory message on Habré dated 2011, so I can’t say what the difference in performance is today. The problem (well, a small one) here is this - if you are writing a project with the goal of making a startup and earning money, then you can use any solutions in pursuit of productivity and ease of support, but if this is a training project for a portfolio or just plan to work in a company - it is better to use Entity Framework AND ADO.NET (teach both) - these 2 technologies are used in the vast majority of existing projects.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question