CSLA 6 save lose data of one field

[Mikael-Pothier]

Hi,

We are trying to update our library to CSLA 6 and we ran into a problem when testing the CRUD operation in a console app. When we do the save operation one of the class properties become empty. All the other properties are fine.

Here is the field in my class, my update method and the code of the console app (I removed all the other field for the example since it didn't seem useful)

This is what happening in Debug. The first image is before the save when my field has data in it and the second is when I get into my update method and the field is empty.

Also, when I was debugging I found out that when it start, the save goes in the constructor which might be where it get the empty array.
Does anyone have an idea why it loses the date of this field?

[saulyt]

GestConcurrence is not declared as a CSLA property, so it is not getting serialized when calling the DataPortal. I'm not sure how it could have worked in a prior version. Perhaps there was no serialization when DataPortal was running local and now there is. Either way, it should be declared as a CSLA property if you are relying on the DataPortal to maintain the state.

public static readonly PropertyInfo<byte> GestConcurrenceProperty = RegisterProperty<byte>(nameof(GestConcurrence));
public byte GestConcurrence
{
	get => ReadProperty(GestConcurrenceProperty);
	private set => LoadProperty(GestConcurrenceProperty, value);
}

[Mikael-Pothier]

Changing for a CSLA property worked perfectly.
Thanks a lot!!

[rockfordlhotka]

I'm sure the app was using BinaryFormatter in the past, and that was fine. Microsoft is deprecating BinaryFormatter, and so CSLA now defaults to its own MobileFormatter.

MobileFormatter requires that you used a managed backing field, or if you use a private field you need to override the get/set state methods and manually get/set your private fields into the serialization stream.