When you use xstream-dot-net to serialize an object that contains
[NonSerialized] fields, it serialized them anyway, which is undesirable and
different than Java's XStream which ignores transient fields.
These fields could be added to the ignore fields list, but that adds
substantial complexity when dealing with an assortment of objects of objects
being serialized. You would always have to have knowledge of the objects
being serialized, potentially asking them via an implemented interface what
fields should not be serialized.
Original issue reported on code.google.com by cgoudien...@gmail.com on 8 Oct 2009 at 4:46
Original issue reported on code.google.com by
cgoudien...@gmail.com
on 8 Oct 2009 at 4:46