Wpf listview binding not updating
There is a huge cost in constructing Resource Dictionaries, and depending on where you place them, you are probably constructing many more objects than you realize.
A common, sensible, and logical pattern is to keep usages of elements as close to where you use them as possible. Resources, or break up their themes into multiple Resource Dictionaries for clarity and separation.
Because of WPF’s references to your objects, it is not just enough to drop references to your view and view model.
A better alternative is to rely on data binding where you can; create a Dependency Property for the sole purpose of listening to changes on your target property, and use the change notifications in Dependency Property in order to listen to changes on the target property.
Blend-style behaviors also have their own set of lifetime problems.It’s painful, but usually necessary in order to prevent view models from taking references to views.If your application displays data from a network, you’re probably using background threads to accomplish the task (which is good).If you have a lot of binding errors, then those split seconds start to add up.
Make sure to go through your bindings, especially those on Items Controls (List Views, custom grids, etc.) and verify that there are no binding errors.Open up your app in the debugger and play around, especially where there is slowness. Relative Source in Data Templates may also result in bindings that break initially, but then later resolve properly.