Entity Framework, when all data access is through stored procedures

Question

The database architect required that all access to the database be done through stored procedures. There is not the slightest place on this. However, is it still possible to use the Entity Framework instead of ADO.NET to call stored procedures?

The Entity Framework has always seemed like an unnecessary extra layer for me, but it had some advantages when updating complex sets of objects that can be nested and have complex relationships. However, now that all access has to be done through the stored procedure, I do not see any additional benefits of the Entity Framework. It seemed to me that ADO.NET is "closer to metal."

But that is why I am asking this question. Are there other benefits to using the Entity Framework when all data must be executed through stored procedures?

Answer 1

Depends on data access strategy.

Are the procedures used to perform the full CRUD operation saved? In this case, the data will not be transferred from the stored procedure, so all Entity Framework will execute it. Although it only takes a few lines of code, the Entity Framework has features like POCOS, models, mappings, etc. that can take thousands of lines of code depending on your database, and you most likely don’t use ( .NET-, - ? Intellisense ). , , . ADO , , Entity Framework ( ).

? (, OLAP) , - . Entity Framework, ADO, , , Entity Framework - , . POCO, -. ADO POCO "", .

, " ", CRUD?. ( ). , , , Entity Framework , , . , Entity Framework, . , :

• ( ?)
• ( ?) , Entity Framework , )
• ( CRUD ?)
• ( - , Entity Framework?)

, .