I have a problem after making our services available to Silverlight.
First off, we have no config files, but some classes which handles hosting and clients. We have a class named ServiceRetriever with methods such as "GetService", "GetDuplexService", etc. So the first thing I did was implementing a Silverlight version of
this class, to support the correct bindings (BasicHttp and PollingHttpDuplex). I've got all this to work, except changing out the DataContractSerializer.
So, I ignorded the DataContractSerializer for now, and tried the services. The first few worked with some IList with quite simple objects. Then I tried calling a service which returns an IList of a quite complex object. Now I'm getting an exception that
the formatter can't deserialize the object because it has no knowledge of it.
Just to make it clear, all the services works when calling them from .NET (WPF app, console, whatever). The only difference is that Silverlight uses BasicHttpBinding, while I use NetTcpBinding in .NET, and I'm not replacing the DataContractSerializerOperationBehavior.
I've also tried adding a reference using "Add Service Reference" (which I by the way dislike strongly, and only use for testing purposes), and I still get the same error from the formatter.
I guess there might be some "bug" in the object causing this problem, but I'm
View Complete Post