Is there a reason why I couldn’t use both EF and ADO.NET in my solution? The latter to handle the more intensive database calls that require faster processing, yet EF for the ORM benefits (code first)???
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a reason why I couldn’t use both EF and ADO.NET in my solution? The latter to handle the more intensive database calls that require faster processing, yet EF for the ORM benefits (code first)???
There might be a misunderstanding, the EF and ADO.NET are actually working together.
Look at the overview MSDN
Also a post that shows usage of stored procedure starting from EF4: A big step for Stored Procedures in EF4