What to study ADO NET or Entity Framework?

Question

.NET

The question is in the title.
If you choose EF, then what is better to study regular EF or Entity Framework Core?

Answer 1

ADO.NET+SQL is required. EF - only if there is no load on your project

Answer 2

I don't know what "smart" moderator thought this question was. Should I use ADO .NET instead of Dapper and EF Core? the same as the current one. The essence of the questions is completely different, even though the letters of some words are the same. Therefore, I answer sergeyiljin to his question.
Everything must have a meaning. EF and Dapper (and ORM in general) were not created "from nothing to do", there was a need for them. A good ORM in the right place makes life easier for a developer, both in code development and code maintenance. Now, on the contrary, they are trying to abstract as much as possible from the use of pure sql and database storage, it is still more convenient to work with the code in one place - both debugging and maintaining are many times easier. And if you work in the OOP paradigm, then it is more convenient for the data to also be close to the object form. Therefore, if you are not in a hard interprise and highload, then there is no point in going into the past. I know one large bank, which a year ago was looking for a new developer for an existing workflow project, where it was necessary to translate all the storages, more than 5k, and sql in the code into EF. Probably not just because they made such a decision.