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 42176 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
Using the "Add Web Reference" wizard on a PCL project generates a Reference.cs that does not compile.
This are the errors I get:
Error CS0234: The type or namespace name `IExtensibleDataObject' does not exist in the namespace `System.Runtime.Serialization'.
Error CS0234: The type or namespace name `ExtensionDataObject' does not exist in the namespace `System.Runtime.Serialization'.
The web service address used was http://api.dreamit.com.br/Handlers/ClienteEcommerce/Acoes.asmx
Xamarin Studio 5.10 and 6.0 both have the same problem on the Mac with Mono 4.4.1.
It is not specific to that particular web service since it is reproducible with other web services (e.g. http://www.w3schools.com/xml/tempconvert.asmx)
Interestingly it works fine on Windows with Xamarin Studio 5.10 and 6.0. On Windows the generated proxy class is different and does not use the IExtensibleDataObject nor the ExtensionDataObject. This possibly points to a Mono problem/change.
Created attachment 16501 [details]
Ran some tests with Xamarin Studio 5.9 and different versions of Mono. Used Xamarin Studio 5.9 since this supports Mono 4.0 whilst later versions of Xamarin Studio do not support it.
In Mono 4.0 the ExtensibleDataObject types are not used but in Mono 4.2 and above they are used.
Windows does not use ExtensibleDataObject however the generated proxy code is different to what Mono generates ignoring the ExtensibleDataObject problem.