Bernard,

A few comments...

- There will always be something new around the bend.

- I never heard that MS would not support SOAP, only that the SOAP Toolkit would not be supported. SOAP is an industry standard and it would be a HUGE mistake for MS to not support it.

- There are probably ways to write the service in fewer lines that I used. I wanted to make the example simple and easy to understand, not necessarily optimized.

- The big deal with WCF is not just web services, but that you can use the EXACT SAME service for web services, internal network calls (think Remoting or COM+), Web services enhancments, and more...and with just changing the config file. No code changes are needed.

>Hi Craig
>
>Thanks for your reply. I also printed and partly read your article. I must finish it soon but time constraints...
>
>Actually you explain very well the benefits etc. and I should have read this thoroughly before replying. It's just that there is some "new" web service technology around the next bend, purpoted to be the best ever.
>
>Last time I looked which was end last year, I was told that SOAP was not going to be supported by MS and so I learn't C# and wrote my web service in that. It was real tough going, but I managed to get it to work and even made it pass data using COM to VFP.
>
>Now along comes this newer tech. WCF with the better claims. I will have to examine it thoroughly, using your walkthrough.
>
>At first glance it seems a helluva lot of extra code and config. For instance the sample you wrote for adding 2 numbers I could have done in C# (and ASMX style web service) in 3 or 4 lines tops.
>
>Anyway thanks for sharing the article.
>
>Bernard