Home/ Questions/Q 4038218
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T12:26:45+00:00

Otherwise than pointed out in this post I would like to act just before

  • 0

Otherwise than pointed out in this post I would like to act just before an XmlSerializer starts deserializing (not when finished deserializing)

Background: I have a baseClass that implements INotifyPropertyChanged. This BaseClass is stored as xml in a database and when retrieved deserialized into an object instance. The deserialization executes the setters of this class where my ChangeNotification takes place. On a centralised handler for the changenotification I set the status of the object and keep track of stacks for undoing changes. Apparently I don’t want these to be trigerred during deserialization.

Any ideas would be very welcome!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As commented @ Marc’s solution. The most pragmatic way right now (I’m developing a proof of concept for a big chunk of complex functionality) is to default the object after it has been deserialized with a simple public void. In this method I can empty the undo stack and set the status of the object to unchanged.

    If I come up with some better ideas I’ll post them here.

    • 0