This articles describes what to have in mind when using the PersistanceFramework to save/load data bound properties.
When you load the preserved layout of a control, the PersistenceFramework goes through the saved properties and sets them on the control. This is a local setting. This means that it has a higher priority than a OneWay binding to the same property. And the values of all properties with OneWay bindings will be overridden by the values loaded from the persistence manager.
To avoid this and use both data bindings and PersistanceFramework, you can use the TwoWay binding mode, which has a higher priority than the local setting. Or you can use the SerializationOptions and exclude the OneWay data bound properties from the save/load process.
Read more about property setting priorities in the Dependency Property Value Precendence MSDN article.
In some situations, the serialized data bound properties could get overridden by the properties from the viewmodel currently in memory. This happens when you call the load method before the data bindings are evaluated.
To avoid this, make sure that the load method is called after the data bindings are evaluated. For example, you can do this in the Loaded event handler of the view.
Example 1: Load the persisted UI in the Loaded event handler
public class MyUserControl : UserControl
this.Loaded += MyUserControl_Loaded;
private void MyUserControl_Loaded(object sender, RoutedEventArgs e)
PersistenceManager manager = new PersistenceManager();