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 14613 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 4829 [details]
Using Xamarin.Android 4.8.
I'd like to swap out the default DataContractSerializationOperationBehavior with a custom class which overrides the CreateSerializer virtual methods to create a custom serializer. Swapping out the behavior before the proxy is opened works fine, but my CreateSerializer methods are never called and the standard DataContractSerializer is always used. Is there a way around this?
I want a custom serializer to work around this problem. http://forums.xamarin.com/discussion/7609/datacontractserializer-does-not-us (Filed as bug 14611)
Most of the time, WCF-related bugs are in the WCF layer, and not Android specific.
Please simplify the testcase to remove any Android dependencies so that WCF devs can more easily fix the bug.