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.
When i run 2 instances of my application in front of a comon SQL SERVER DB i have the following behavior:
each time an object is added or removed, the other app sees it
each time an update is done to the object, the other does not see it until i close and open the application
I’m working with WPF bindings and EF4
Any clue ?
thanks
Joghn
I think you are reusing context, don’t you? EF will not load changes automatically. If you run the query, then modify data in the database and then run the same query again you will get the same result as in the first query, only new records will be added. That is how EF behaves and this behavior is very important in ORM tools. If you want to force context to reload data and throw away the state you have in the application (= all unsaved changes will be lost) you must run the query with
MergeOption.OverwriteChanges(example here) or callRefreshmethod withRefreshMode.StoreWins.