WCF, as defined by SOA, must not transport an object (state and behavior), only the state and strucuture of an object. BinaryFormatter, and SoapFormatter are inadequate for SOA because: 1) Requires both ends to share type 2) cannot be used for contracts 3) both formatters require streams.
I had XmlSerializerFormat at the top of my contract interface. Removing it fixed the problem, as WCF starts using the default DataSerializerFormat. Thanks Darin for point it out.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.