Bug 1551 - MonoDevelop should use svcutil --monotouch to generate WCF client proxies
Summary: MonoDevelop should use svcutil --monotouch to generate WCF client proxies
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Web Services ()
Version: 2.6
Hardware: PC Mac OS
: Highest normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
Depends on:
Reported: 2011-10-18 16:22 UTC by Joseph Hill
Modified: 2011-12-22 21:15 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Joseph Hill 2011-10-18 16:22:32 UTC
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:

svcutil --monotouch

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.
Comment 1 Alan McGovern 2011-11-16 17:56:11 UTC
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?
Comment 2 Mikayla Hutchinson [MSFT] 2011-12-22 21:14:55 UTC
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.