DataContractSerialization does not call the constructor of the objects that it deserializes. This decision was made because with previous serialization methods in .NET, which should always have a default constructor for any object to be serialized, is a problem. This does not apply to RIA Services, it was a design decision taken when creating the WCF itself, and there is no configuration to change it.
Further information can be found at http://blogs.msdn.com/b/carlosfigueira/archive/2011/09/06/wcf-extensibility-serialization-callbacks.aspx , as well as examples of how you can use [OnDeserialized] for constructor effect replications called.
However, there is a second problem that can cause problems. Objects are constantly being created. For example, at any time when you call TEntity.GetOriginal, a newly created object is created and returned from the method. This makes an attempt to do something like tuning RelayCommand to a potential performance and stability issue. You should probably configure RelayCommands at the DataService or ViewModel level, rather than inside the object itself.
source share