>Much like having a WebService return a DataSet. That'll work with a .NET client easily enough, but not with other clients unless you use the XMLDOM to parse the object that's returned, since it *is* an object that's returned, not an XML string. So, bottom line with that is never return a DataSet, return DataSet.GetXML() instead.
>Same goes for this overloading stuff ... it's probably not standard behavior, so don't do it.


Those are very good points. Really, if the Web Service is going to be available public, we need to keep straight to the standard. The other stuff (datasets, overloading, etc), may just be used when we do have control over the client.

Good to have that in mind. Thanks. :)