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.
Possible Duplicate:
ObjectContext vs DbContext
The author of this answer wrote that https://stackoverflow.com/a/12494339/1662812 “Both T4 and DbContext API are currently recommended approach for using EF”
I still wonder what exactly is the difference between DbContext API and ObjectContext API when used with Entity Data Model and I am also looking for any reference about DbContext API being recommended approach for using EF.
“DbContext is much simpler to use than ObjectContext and will serve the most common development needs. if you need more, you can drop down into the ObjectContext.
Remember that DbContext sits on top of the ObjectContext. The ObjectContext is always there in the background doing it’s work. So if you need to do something very granular, DbContext provides a hook to its underlying ObjectContext.” from http://thedatafarm.com/blog/data-access/code-first-and-dbcontext-are-now-ldquo-the-entity-framework-rdquo/.
She is in EF team, also has good video about that on Pluralsight.
From my point of view, DbContext is easier to use, and covers almost everything you need. I always make an extension method for exposing object context (methods from it) if I need them somewhere.