>- What would you like to see Microsoft add to VFP to make creating XML Web services easier?

Considering this is Visual FoxPro, in VFP8 you should be able to create these classes visually without loosing any features that you get by doing them in code. In fact, all classes should be editted visually. I'm not saying they need to be stored in a VCX, just that we can edit PRG based (or XML based?) classes in the Visual editors.

A nice little Tester for Web Services would be helpful. For example, you give it a WSDL, and it shows you a list of functions you can call. You choose a function, and populate the parameters it prompts you for, and then shows you the result of the call. If its a failure, a decent explanation of why it failed would be given.

An IIS anyalzer would be handy. A little tool that tells you if IIS is setup right, or a firewall is in the way (IIRC, with XP pro the ICF automatically blocks Web Service hits so if you wanna demo it you might have a tough time getting at it). If FoxISAPI isn't installed, and you build an ISAPI listener, it shoudl probably say something. Samething if the SOAP Toolkit isn't installed.