>I am not sure I follow your process below... Bascially, you create the web service project in .NET which yields a asmx file. Assuming the project is called test, you can get the wsdl like this:
>
>http://localhost/pubs/pubs.asmx?wsdl
>
>Intrestingly enough, while you can access the web service in VFP 7, the intellisense doe not work.
>
>IAC, if you are working in .NET, you simply add a web reference by pointing to the asmx URL. Consuming web services, whether you are in VFP or .NET is a snap. Creating web services OTOH, I find to be streamlined in .NET.

Ah, but you're making assumptions. The *development environment* is doing that, not .NET itself. If you do all of this manually, guess what? It takes about the same number of steps in .NET as VFP...

A Web Reference is really a proxy object that VS generates and injects into your project and that object is hardcoded with the WSDL path and a few other things. Now if you recompile VS goes out and checks to see if something's changed and if it has recompiles the proxy.

I've built wwSOAP a long time ago around the same principal - by creating a VFP proxy object around the call wrapper you get a single object instance that's fully VFP capable including Intellisense.

My point here is that this can be done in VFP just the same and in fact in my environment is automatic (granted I wrote that, but that's a simple automation procedure). It's a Dev Environment issue which simply means the VS people included it into the shell. The VFP team can do the same type of thing with very little effort. Today any developer who uses the SOAP Toolkit can do this by adding a project hook and automating the WSDL wizard or with Web Connection use the SoapHelper class to generate the WSDL on the fly from that same hook. In either case it's a handful of lines of code that are canned.