Y
Youcef
I started developing an ASP.NET web service by explicitly
designing the WSDL and separating the data type definitions into XSD
files. I followed the steps described in the following MSDN article to
enlist the help of VS.NET in doing this through the use of separate
namespaces and the [WebServiceBindingAttribute]. See :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/service08202002.asp
But I found that I couldn't pass an XML Schema ComplexType (e.g. an
address class) as an input parameter to one of the methods of the web
service !! If I pass a simple type or I move the same complextype
parameter as a return value from the method, VS.NET 2003 generates the
right stuff and the method is listed among the available methods for
the web service . I spent 2 days checking and re-checking everything
to no avail. This must be a bug, but I couldn't find it mentioned
anywhere. Has anybody tried this ?
designing the WSDL and separating the data type definitions into XSD
files. I followed the steps described in the following MSDN article to
enlist the help of VS.NET in doing this through the use of separate
namespaces and the [WebServiceBindingAttribute]. See :
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/service08202002.asp
But I found that I couldn't pass an XML Schema ComplexType (e.g. an
address class) as an input parameter to one of the methods of the web
service !! If I pass a simple type or I move the same complextype
parameter as a return value from the method, VS.NET 2003 generates the
right stuff and the method is listed among the available methods for
the web service . I spent 2 days checking and re-checking everything
to no avail. This must be a bug, but I couldn't find it mentioned
anywhere. Has anybody tried this ?