[Mono-list] Forcing MONO to create VS compatible WSDL file for Web Service

Andrus kobruleht2 at hot.ee
Sun Dec 28 16:25:06 EST 2008


Web method code (Test.asmx):

[WebService(Namespace = "http://Myappl.com/myapp")]
public sealed class Document
    {
        [WebMethod]
        public string SaveAssetDocument(Dok dok, List<Rid> rid)
        {
...


VS2008 service proxy code creator generates different signatures for this
method async proxy:

For web service running under MONO SVN:

public
DocumentServiceReference.DocumentSoapClient.SaveAssetDocumentAsync(DocumentServiceReference.Dok,
DocumentServiceReference.ArrayOfRid1)

Same web service running under .NET 3.5SP1

public
DocumentServiceReference.DocumentSoapClient.SaveAssetDocumentAsync(DocumentServiceReference.Dok,
DocumentServiceReference.Rid[])

MONO web service method signature contains intermediate type ArrayOfRid1 :

[System.Runtime.Serialization.CollectionDataContractAttribute(Name="ArrayOfRid1", 
Namespace="http://Myappl.com/myapp", ItemName="Rid")]
public class ArrayOfRid1 : 
System.Collections.ObjectModel.ObservableCollection<DocumentServiceReference.Rid> 
{
    }


while VS web service contains array type.
So code which works with VS service causes compile error running with MONO
service.
Probably wsdl files are different which causes different signature
generation.

How to force MONO to create VS compatible wsdl file ?

Andrus. 



More information about the Mono-list mailing list