OK, so your WebService is just returning a string, correct? Normally I'd say that optimally a WebService should return XML, but in this case, since they are only returning a single string, XML may be overkill. I don't know what the "best practices" would be in this case, but it seems to me that it's simple enough to just leave it at returning a simple string.

Maybe someone else can jump in with some other ideas ...

~~Bonnie

>Currently I have some web services that garner release info from an SQL server and report the release. Additionally I have some that return a status based on backend actions. So its single element items for now.
>
>Joe.
>
>>Joe,
>>
>>I'd say it depends on what you're doing with what the Web Service returns. We only use our WebServices to return DataSets to our WinApp that have been serialized to XML (return MyDataSet.GetXML()). Is that the kind of thing you want to do?
>>
>>~~Bonnie
>>
>>
>>>Everyone please forgive my extended absence.
>>>
>>>How does your app parse the returned data? Did you write a straight parser? ... I am interested in utilizing web services for a large number of tasks.
>>>
>>>My thanks in advance,
>>>Joe.
>>>
>>>>Joe,
>>>>
>>>>The application that our company is working on does just that...a bunch of Winforms that access a Web Service, and pass a request on to the middle tier. We've gone through the learning curve [thanks in no small way to different people here on the Thread].
>>>>
>>>>Doo you have any specific questions?
>>>>
>>>>Kevin