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.
Mono's svcutil will generate MonoTouch-compatible and Mono for Android-compatible WCF client proxy code if called with the --monotouch option. No one knows this or how to discover this (and most users think the best answer is to generate the proxy with the slsvcutil that ships with the Silverlight SDK).
We should integrate svcutil into MonoDevelop for generating these proxies with WCF services are referenced from MonoTouch and/or Mono for Android libraries:
Possibly we should just consider always using that option to generate these proxies.
svcutil ships with Mono on OS X and Windows; however, MonoDevelop on Windows does not require Mono, so we may need to ship our svcutil with Mono for Android on Windows.
Related issues i'm too lazy to file a bug for:
1) Cannot open the generated .cs file in the references thing
2) Generating a WCF reference blows up, .NET 2.0 reference works
3) Duplicate assembly references
4) Android and MonoTouch projects should use either the silverlight svcutil *or* it should use the mono one with --monotouch. Be wary of using the Microsoft .NET version as it may not work.
5) Service References are weird, should be like web references?
Should be fixed in git, but I don't have any test cases to verify. MonoDevelop had already imported a copy of the svcutil code, and was using the --monotouch codepath for MT but not for M4A.
Alan, if you have real issues to report, please file bugs.