Dynamic Data VS LiveData

In the realm of .NET development, managing collections and their changes can be a challenging task, especially in applications with complex data flows and user interfaces. This is where DynamicData, a library in the .NET ecosystem, comes into play. It simplifies reactive data management, making it easier for developers to handle complex data operations with ease. This article aims to provide a comprehensive understanding of DynamicData, its core concepts, and practical applications.

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

With DynamicData you can use a ObservableCollectionExtended for your list and call .ToObservableChangeSet().WhenAnyPropertyChanged().Subscribe(t => { code to execute });

reminds a lot of https://github.com/reactivemarbles/DynamicData

If you're trying to use reactive with MVVM, you might have a look at ReactiveUI, an MVVM toolkit designed to work with reactive extensions. Specifically in this case, you could leverage DynamicData (RXUI's preferred method of handling collections), which lets you trigger updates based on change notification from child items, among other things. I'm still relatively new to RXUI myself, but if you have any questions I can certainly try to help a bit more.

Right and I never said they did. I said replace the observablecollection with an iobservable if you want it to be observable. You can then use https://github.com/reactivemarbles/DynamicData to get yourself an observablecollection. I'm not arguing that observablecollection + linq would result in an observablecollection. Just pointing out that there is a solution for this.