Recently I have been messing around with figuring out how to serialize some data back & forth between two applications. The code in particular leveraged several.

The missing ingredient is the [Serializable] modifier on the class (in my case, my fields class). So while a List may be 'serializable' when named as a DataMember of a DataContract the members of the class are not serialized inspite of the fact that they are themselves serializable, such as a 'string' is serializable. Html And Xhtml 5th Edition Tutorial 2 Review here. In my particular case the fact that the Serializable modifier causes all members to be serialized is of no real consequence since it is really a 'struct' with its sole purpose for existing is to hold the fields that I want serialized. It is kind of an intermediate class to hold just those things that I want on the wire anyway. I think that this satisfies the purist to a large degree. I am a purist in theory, and a pragmist because I get paid when it works.

Thank you everyone, this has been an experience. List is indeed serialized, but the you insert isn't, or at least not automatically. And your class kind of becomes a part of your List.

When you mark a class as [Serializble] that class is suddenly. Well, serializable. It's just that now everything is serialized, also private attributes.

The service orienated tenet that boundaries are explicit doesn't count anymore now, according to purists. Just use DataContract and DataMember on class and fields to specifiy what must be serialized. It uses a new data contract serializer that was introduced with.NET Framework 3.0/WCF. The missing ingredient is the [Serializable] modifier on the class (in my case, my fields class). So while a List may be 'serializable' when named as a DataMember of a DataContract the members of the class are not serialized inspite of the fact that they are themselves serializable, such as a 'string' is serializable. In my particular case the fact that the Serializable modifier causes all members to be serialized is of no real consequence since it is really a 'struct' with its sole purpose for existing is to hold the fields that I want serialized. It is kind of an intermediate class to hold just those things that I want on the wire anyway.

I think that this satisfies the purist to a large degree. I am a purist in theory, and a pragmist because I get paid when it works. Thank you everyone, this has been an experience. Articolo 31 Disco Grafia Completa De Dulce more.