>John, the point is MS and Ken aren't even supporting the basic web services stuff or components or web stuff for vfp. No wonder not as many people are using them. Check out the dwindling web examples in each new version of .vfp. And I would argue that creating web apps is far easier using vfp and existing code and skills that creating a brand new one in .NET.
>Ken and MS are not promoting them at the conferences and they probably have some input over what gets published in the mags (maybe, maybe not, but advertising dollars pay the bills). I would argue that this plays into the strategy of Ken and MS to get everybody to buy both .vfp. and vs.net. The people who lose, of course, are the developers who would have to spend the time and money rewriting everything. A good middle-ground would be more support for interop between .vfp. and .net ...

What do you mean we are not supporting it? Ther are demos of VFP working with XML Web services and COM/.NET interop in every keynote session we do for the past year and more. Consuming an XML web service in VFP is very easy, and there are lots of samples and documentation on that topic. For publishing an XML Web service from VFP, the best way is to have an ASP.NET XML Web service be the wrapper and simply call a VFP COM DLL. There are articles on using the XMLAdapter with ADO.NET online, using the VFP OLE DB provider to access VFP data from VS .NET, etc. As I said in reply to your other post about this...

It would be useful for you to list what specifically you think is needed, not generalizations like this. There are several whitepapers on this on MSDN for VFP, there are samples to download at http://gotdotnet.com/team/vfp, there are many whitepapers on Rick Strahl's web site http://west-wind.com on this (which we would not need to reproduce on MSDN since these are good articles), etc. If you list out exactly what you think is needed, I could get input from others wanting similar materials to help figure out what should be the highest priority items.