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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
In order to establish a connection between a Xamarin.iOS client and a SOAP 1.1 service, you client-side have to foresee the service's DNS identity.
Using method DnsEndpointIdentity(string) this leads to a runtime error "System.NotImplementedException: The method or operation is not implemented.".
As the method is part of the System.ServiceModel 220.127.116.11 assembly, I wouldn't have expected such a "behaviour". Furthermore, I do not know a work around. It seems to be a show stopper.
According to the mono source code the behavior you are seeing is correct. The Web services technologies that Xamarin supports can be found here[2/3]. That being said there are some limitations for example in WCF, if you want to generate a proxy file that works with us you would need to use SLsvcUtil.exe from the silverlight toolkit.
Another thing you could do is wrap your service with a REST service and have your Xamarin app consume the REST service.
Hope this helps.