.net - When should you not use an ObservableCollection and Databinding? -

Dipton helped me to think about why you do not want to use the Observeable Collection in some circumstances?

When you want more control over the notifications sent by the Observe Collection. Example: Default implementation, while it supports the addition of categories of elements, instead of food, instead of food, a reset for the entire collection (I believe) throws the same notification with all the new items on it This is a part of this because the default archive view in WPF does not support INotifyCollectionChanged NotesSize> 1 (It throws if you do so), so that more pre-production for it Krishna is not. However, if you are using a third-party grid, such as AXD, then there is a collection view derivative in it, which does supports uncontrolled notification sizes, this means that when you have a If you are collecting data in the list, you can get some very good barriers to performance by grouping the information.

Note that there are some interesting inventory points related to the notification size, and priority notifications which are supposed to be performed, and actual performance (both of which you think both are).

This is a primary example of why you want to loose your interface: we type as IList, and our implementation is our own, async-loading collection, Because we load the clauses of the data. See, this is not known about the difference. It just works.