If it handles round-tripping these fields and lets me get rid of this code,, then yes. Specifically, fields like _editLevelAdded, _identity, etc. Right now I generate code that uses UnsafeAccessor to help a bit with Reflection performance, and the goal of this feature would be that I wouldn't care about any of this. I could tell a BO to serialize its state and/or metastate, and it would just work.

But, the way this is implemented, there's still Reflection involved. I'm not sure that's ideal. Couldn't each BO implement IMobileObjectMetastate, which would make it such that it knows which metastate fields to roundtrip, and that would eliminate Reflection usage altogether?

Basically, IMobileObjectMetastate is fine. But I don't get why MobileObjectMetastateHelper is there, using Reflection to do the work. Seems like each stereotype should implement this and handle its fields directly.

The updated implementation is much simpler - doesn't use the StateMode property and therefore only works for serialization, not undo. By doing this it eliminates the need for reflection.

@JasonBock you don't care what is in the byte array I assume? It is JSON in this case, but you are just going to treat it like a blob I assume?

The updated implementation is much simpler - doesn't use the StateMode property and therefore only works for serialization, not undo. By doing this it eliminates the need for reflection.

@JasonBock you don't care what is in the byte array I assume? It is JSON in this case, but you are just going to treat it like a blob I assume?

Correct, I don't care what's in the array. I assume the implementor knows what they're doing ;)

Correct, I don't care what's in the array. I assume the implementor knows what they're doing ;)

That's just silliness!