I have a smart client application communicating with its server via WCF. Data is created on the client and then sent over the service to be persisted. The server and client use
Ok just came across another scenario on this one. I had a Serializable type used as a parameter for one of my Operation Contract methods.
Commenting out this specific method from use allowed me to find the issue. In this case, the parameter was a model deserialized from a file, so I just replaced the implementation with a parameter of byte[] and ran deserialization logic at the other end.
While not necessarily an answer for all, in the case of parameter types on your Operation Contract methods that are Serializable, you may run into this exception also. I would imagine decorating them with correct DataContract attributes would assist in rectifying this problem.