The PersistenceFramework should be aware if any new UIElements are added to a layout it persists.
Add SaveToStorage method to the IsolatedStorageProvider that takes as parameters a list of the StorageIds to be saved.
The XmlSerializer constructor generates a new assembly every time you save your layout and this causes performance and memory issues.
Info for the root object needed in PErsistenceError event
Calling GetIsolatedStoreOverride returns a wrong Isolated storage. Available in LIB version: 2015.1.1105
Will be available in Q3 2015 Release.
Extend the PersistenceFramework to load the persisted settings of an earlier version of an application.
A first chance exception of type System.IO.FileNotFoundException is thrown by the IsolatedStoragetProvider when calling its SaveToStorage() method. Note: the exception does not prevent the manager from saving the UI. To see the error you will need to enable the CLR exceptions from the Visual Studio's Debug-->Exceptions menu Available in LIB version: 2015.1.1805
PersistenceFramework does not persist property of type byte in CustomPropertyProvider scenario. Use List<byte> as a workaround if applicable.
RadRichTextBox (RTB) is used in MainWindow and no other controls are used.
Here is an example exception: Types 'Telerik.Windows.Diagrams.Core.SelectionMode' and 'System.Windows.Controls.SelectionMode' both use the XML type name, 'SelectionMode', from namespace ''. Use XML attributes to specify a unique XML name and/or namespace for the type.
As a workaround, you can exclude the property with the repeating name as demonstrated in Example 4 in the following article: Serialization Options
Does not save correctly \r\n entries. When we load the stored date only "\n" is returned and the \r is lost.