i am upgrading an old project that uses .NET 3.5 and Telerik UI for WPF 2012.x to the latest .NET and Telerik UI versions. I have a GridView whose ItemsSource is bound to a RadObservableCollection provided by a MVVM viewmodel. As i rememder i used this collection because of the RemoveRange-method which had some performance benefits compared to the ObservableCollection.Remove-method (suspending the collectionchanged-events).
But now i have the problem, that, if a least one column is sorted, not the correct rows are removed. The rows removed are those, that are in the place of the rows i want to delete if the table were unsorted. Deleting from an unsorted GridView works fine. If i use the Remove-method in a loop instead of the RemoveRange deleting works as expected in sorted and unsorted GridViews.
Is it not longer recommended to use the RadObservableCollection as an ItemsSource for a GridView or is it a bug?