The requirements that you described for properly saving the App
state would be correct. And based on my understanding,
would not be able to know how each ViewModel
would be expected to save its state as this behavior would depend on the
In addition, it may exists autocalculated properties or some private ones that would not be expected to save its state because they would get their corresponding value when interacting with some other elements.
If you would like to save the state of all ViewModel's
properties, you could also modify the
class or create your custom one in order to not validate the properties list having the
defined, on the FillStateDictionary()
methods. Therefore, those methods would iterate through all ViewModel's properties without having to declare the
atrribute on each of them.
Anyway, if you would think that the automatic save and restore should be provided by
without the need of using RestorableState
attributes you could create an item in the Issues section of this site so the
would look into your feedback.