Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 27510 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 10089 [details]
When a WCF service implements a method which has a return type which is an interface, and the ServiceKnownType attribute is used to register the concrete implementation, it is ignored and a System.Runtime.Serialization.SerializationException is thrown.
When running the same code under .NET, it works fine.
The attached solution demonstrates the problem - when running in .NET it works, when running with mono you will see the following error when the server tries to respond:
Exception Type 'Common.ResponseImpl' is unexpected. The type should either be re
gistered as a known type, or DataContractResolver should be used.
The behaviour therefore seems to be different between mono and .NET, so I believe it is a bug.
Is anyone aware of a workaround other than re-implementing to not use interfaces as the return type?