Bug 6854 - ASMX WebService registration failure
Summary: ASMX WebService registration failure
Alias: None
Product: MonoMac
Classification: Desktop
Component: Bindings ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-09-03 05:53 UTC by Henrik W.
Modified: 2015-02-17 14:14 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 Henrik W. 2012-09-03 05:53:30 UTC
I am adding a reference to an asmx webservice and the reference.cs file that gets generated contains duplicates.

I can add this reference just fine in VS2010 and methods and delegates with similar signature gets renamed automatically, for example:

        private System.Threading.SendOrPostCallback GetUserGroupsByGroupNameOperationCompleted;
        private System.Threading.SendOrPostCallback GetUserGroupsByGroupName1OperationCompleted;

Notice the 1 inserted automatically.

I assume that they are duplicates since they have overloads.
Comment 1 Chris Hamons 2015-02-17 14:14:39 UTC

Sorry for the delay in response. It was misfiled and overlooked.

I'm not sure this bug has enough information for me to track down the problem. Given the length of time it has been since it was reported, I'm going to close it. Please open a new bug if the problem still exists.

Apologies again on the delay.