wpf - Transactional objects in .NET -

The cancel button needs to be implemented when editing certain entities in the user interface. Visual models can make transactional. I will try to explain a bit more detail in detail which means:

The visual model is connected to the model and exposes the data in such a way that it is easy to handle for the scene (using data binding Do) changes in model change as a result of change in model However, if there is a cancellation button, then you usually do not want to change the model immediately, so I think about any type of buffering changes. When you make changes, the model is being moved, otherwise they are removed.

I have now implemented a solution that creates a proxy of the visual model that is not connected to the real visual model proxy model instead of the scene, but using the interceptor changes records in properties and method calls. There is a submission method that applies to invoices on the real visual model. I think this is a very good solution, but it's still quite a buggy (if the visual model is collection and so on).

I'm looking for a framework that does this kind of stuff

Only binding verification If you are not, you can use Edit, Commit Edit, and Cancel Edit to start a binding group to enable transaction logic. If you are a pure MVVM type then there is one thing that can be a problem for you - you will get some code in your thoughts - otherwise it works like a magic.