>Bernard,
>
>A few comments...
>
>- There will always be something new around the bend.

I know. Just thinking aloud.

>
>- 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.

Yes. My mistake.

>
>- 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.

I meant that writing the ASMX service took just a few lines. With WCF there are a number of steps and classes and processes that need to be done before actuallygetting the service to work.
>
>- 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.

Like I said, reading and digesting the complete article is onmy To-Do list.

Bernard