Hi Ross,
Actually... imagine the following service operation:
[WebMethod]
public DataSet FindCustomerOrder(string customerId) {}
With an ASP.NET Web Services you can create a full-blown web service by
decorating an arbitrary method with the WebMethod attribute. The .NET Web
Services infrastructure will then serialize the resulting DataSet to an XML
message and pass it on the wire. The consumer of your service (non .NET
consumer) receives the XML message as plain text. In case you use the Web
Service wizard in Visual Studio.NET it will autogenerate a proxy which lets
you believe objects are passed across the wire but underneath the
infrastructure takes care of serializing/deserialising your objects
instances to XML messages and visa versa. I would certainly advise you to
read up on ASP.NET Web Service internals to get a complete picture
(
http://msdn.microsoft.com/webservices/).
Whether or not it is the right thing to use .NET specific objects in your
web services is another discussion.
Best regards,
Paul Gielens
Visit my blog @
http://weblogs.asp.net/pgielens/ ###
[quoted text, click to view] "Ross" <Ross@discussions.microsoft.com> wrote in message
news:93EB97F2-5B4E-4BDD-96DB-233963142D89@microsoft.com...
> Hi folks
>
> I am told that for interop purposes it is better to have a procedure that
> returns XML rather than a DataSet.
>
> How do you do this?
>
> Is it just a matter of having a public function (with WebMethod) that
> returns XML?
> eg Public function(args) as XML
>
> etc
>
> Then in the body of the function using the fill method of the DataAdaptor.
> eg adAdaptor.Fill(xml variable)
> return(xmlvariable)
>
> or something like that?
>
> If somebody could head me in the right direction I would muchly appreciate
> it.
>
> Kind regards & thanks in advance
>
> Ross Petersen
>