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.
This is a big issue for me. I want to write a WPF / MVVM application that fetches data from an online WCF service.
Problem is, that the fetching process must be every, say, 15 seconds (it’s a time critical application).
There is an everchanging IEnumerable involved, every time I check the WCF service, I WILL get different values, because there is also time data involved.
How would I go about that? Clearing the ObservableCollection in the ViewModel can’t be right, or is it?
Suspending and resuming change updates on your ObservableCollection could be an approach:
See answer: ItemsControl.ItemsSource MVVM performance
In this way you can suspend whilst you clear down your collection and update it, then resume when you’re done. This approach should mitigate issue with mangling the collection and generating lots of change update events.