>>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 ...
>>
>
>
>Two points:
>
>First - prior to .NET - Fox supported web services as well as any other COM dev tool - and yet there was not wide adoption.
>
>Second - Rod Paddock took a straw poll up here to guage how many Fox developers actively use COM Components/Web Services. Results - not many.

When you say COM components do you mean using OLE PUBLIC and building the VFP project into a .dll?

I think a lot more VFP developers build COM components compared to build web services....

its a shame because the web service support in VFP 8 is amazing, IMHO.



>
>< JVP >