Hi,
we are using our own IPagedCollectionView implementation in combination with the RadDataPager control as shown in the attached example project. Basically, we bind an instance of the PagedCollectionView that is provided by our ViewModel to the Source property of the RadDataPager.
Recently we started to take implementing the Dispose pattern a bot more seriously and also added the IDisposable interface to our custom PagedCollectionView (in order to Dispose some internally used CancellationTokenSource). Today we realized that the RadDataPager now calls Dispose() on the PagedCollectionView instance although not being its owner. This happens as soon as the DataPager itself is Disposed e.g. by switching modules (and thus loading a new DataTemplate) in our multi-module application. Coming back to the module will then cause the disposed Collection to be used again, potentially causing ObjectDisposedExceptions etc.
What I would expect: The RadDataPager control should not call Dispose() on its Source collection if it is Data-Bound to a ViewModel since that might leave the ViewModel in an invalid state that can cause Exceptions later on.
The problem exists with .net 6 and .net Framework 4.8 as well as with versions 2022.3.1109 (Xaml, see Example project) and 2022.2.621 (NoXaml)
