>>Claudio -

Hi, John.

>>>For these reasons - the web services created in VS .NET are probably a bit cleaner since you don't have the COM Layer. I could be wrong here, but having a Component Object Model layer keeps a lot of those same old problems around.

got it... I´m planning to take a good look at C# to build some WS stuff...
could you tell me about some good literature about it?


>>>In my opinion, learning web services in VFP is a good thing because it makes for a familar environment. Developers should then take the next leap to tinker around with web services in VS .NET. Rick has posted some very good samples that illustrate the use of WEB Services in data and non/data scenarios.

I´ll take a look at Rick´s Articles (you meant those in his web-site, doesn´t you?)

Also, Rick gave me a very nice interview to be published on RapoZine, and also on UTMag, and he had explained very well why VFPers must take a look at .NET.

anyway, until now I stiil though that create a class in VFP is much straightforward than it´s in C#, with all that {}(); stuff. :)

thanks for your thoughts.