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.
For the entity framework context, the best practice is to only have your context hanging around for as long as you need it. Does the same thing hold true for a Silverlight Domain Context or is it “safer” to hold it for longer? If you can instantiate it once and make it an application scope variable, could you add it to the ApplicationLifeTimeObjects list?
A DomainContext is just a change-set, so the use of it is determined more by your business rules.
So long as you save out changes, to avoid data loss, I am not aware of any reason to stop you reusing one only DataContext for the life of the application.