I tried to use the ObservableObject (WPF4, 220.127.116.1113) for a small model, which has to be serialized. But I got a Runtime.Serialization.SerializationException:
The german message is:
Der Typ "GalaSoft.MvvmLight.ObservableObject" in Assembly "GalaSoft.MvvmLight.WPF4, Version=18.104.22.16813, Culture=neutral, PublicKeyToken=63eb5c012e0b3c1c" ist nicht als serialisierbar gekennzeichnet.
Which means: The typ ObservableObject ... is not marked as serializable.
If I follow the MIX 11 video and thought that ObservableObject should be serializable. First the "Friend class" should be small and serializable and at about 10:00 min it inherits from ObservableObject.
See also: http://mvvmlight.codeplex.com/discussions/349115
lbugnion, May 21 at 8:54 AM
The choice to work with INPC on the Model is driven by simplicity. Using a DO there is overkill because DOs are quite heavy and "drag" with them a lot of features that only make sense on a UI. For instance,
DOs are not serializable while INPC implementations are, of course.
In MVVM Light V4, you can use the ObservableObject class and derive from this.
Is this a misunderstanding or a bug?