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 14343 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
The bug I am about to describe is rather a small thing although it cause error in application runtime.
There is a small yet importatn diference between message generation on mono linux and C# windows environments.
When message is generated it has an Action node in header. On windows it looks like this:
while on linux it looks like this:
this little diference (missing "urn:") causes that deserialization works incorrect.
To be more occurate we create message on linux and deserialize it on windows. Problem occured when we passed FaultException<> with specific inner exception. Windows deserialization didint recognized that FaultException was of generic type and didin't deserialized the inner exception.
In our application we needed that information for proper error handling.
a very ugly but solving the problem fix can be found here: