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.
I am developing an MVC3 application and have been wondering about the following. Should the Entity Framework object (DbContext object) be disposed before passing data to the view?
The obvious issue with this is you will not be able to drill down into the foreign key relations.
Is there a performance hit by doing this?
Yes you absolutely should dispose of the context
The performance hit should be minimal . Any object that can be disposed of should be disposed of ALWAYS.
Dependency injection can free you from having to worry about calling it if done properly as the DI framework will dispose of it for you if instructed.