You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested it but unfortunately it doesn't fit my need.
You introduced a new class called SerializableChangeTrackingCollection<T> but you used it only at client side, doing this way you are able to serialize just the hidden properties (the deletedEntities) at the root level.
I try to explain better:
The client retrieves 6 Order and it puts these 6 Order into a SerializableChangeTrackingCollection<Order> collection, now the client delete some item of this collection and in this way when this object is serialized it keep the info about the deleted Orders.
_It Works!!_
_But it is not enough_ because I need the same behaviour also for all the recurive collections present into the graph (for any navigation properties into the POCOs).
Imagine a different Example (I'll commit this sample into my fork asap):
The client retrieve 1 Order together with all its OrderDetails (OrderDetails is a collection of OrderDetail) and it puts this Order into a SerializableChangeTrackingCollection<Order> collection, now the client is hosting just one Order into the SerializableChangeTrackingCollection<Order> collection and that Order has a collection of many OrderDetail; if the client deletes some of those OrderDetail, since they are not "Serializable..", the information about their deletion will be lost when we serialize and deserialize the client SerializableChangeTrackingCollection<Order> collection.
The text was updated successfully, but these errors were encountered:
Quick answer. Can you change the type of the OrderDetails property on Order from ChangeTrackingCollection<OrderDetail> to SerializableChangeTrackingCollection<OrderDetail>?
I tested it but unfortunately it doesn't fit my need.
You introduced a new class called SerializableChangeTrackingCollection<T> but you used it only at client side, doing this way you are able to serialize just the hidden properties (the deletedEntities) at the root level.
I try to explain better:
The client retrieves 6 Order and it puts these 6 Order into a SerializableChangeTrackingCollection<Order> collection, now the client delete some item of this collection and in this way when this object is serialized it keep the info about the deleted Orders.
_It Works!!_
_But it is not enough_ because I need the same behaviour also for all the recurive collections present into the graph (for any navigation properties into the POCOs).
Imagine a different Example (I'll commit this sample into my fork asap):
The client retrieve 1 Order together with all its OrderDetails (OrderDetails is a collection of OrderDetail) and it puts this Order into a SerializableChangeTrackingCollection<Order> collection, now the client is hosting just one Order into the SerializableChangeTrackingCollection<Order> collection and that Order has a collection of many OrderDetail; if the client deletes some of those OrderDetail, since they are not "Serializable..", the information about their deletion will be lost when we serialize and deserialize the client SerializableChangeTrackingCollection<Order> collection.
The text was updated successfully, but these errors were encountered: