>There should not be a "use ASMX instead of SOAP". ASMX uses SOAP as it's transport mechanism. WCF is Microsoft's latest technology that replaces ASMX, MSMQ, COM+, and .NET remoting into a single technology with a single API. Microsoft's tests have shown it is up to 40% faster than ASMX and remoting. Compared to those two technologies, it is easier to code and configure. It is also SOA-based. WCF in .Net 3.5 can also be either SOAP or REST based.
>
>>Just a few months ago people said ASMX over SOAP. Now WTF over ASMX? Why?

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