>This is a bug that was never fixed and continues to be a problem. It's a simple thing but it just highlights exactly how crickety the SOAP Toolkit really is. MS doesn't care much about this product any more in the face of .Net - it's little more than a stop over, legacy tool that is supposed to get people working with Web Services before switching to the easier Web Services implementation in .Net. I don't expect that to change.
>
>Imagine somebody who barely knows what a Web Service is, doesn't read the docs or a Video as Marty did (and Marty's been around coding for a long time!) how it would be next to impossible to figure out that the ISAPI listener just wasn't installed correctly. The install doesn't even have the decency to provide a check application that can tell that everything works correctly via installation...
>
>Yet we have tools that generate Web Services automatically from a project now, without any chance of checking whether the installation is even there.
>
>Something is wrong with this approach...

I agree with everything you said.