Hey John,

Thanks for clarification. The page still states VB and VC++ and is quite leading. Here's the paragraph.

The code that follows uses Visual Basic®, but the same tools for simplifying Web service creation are available in other Visual Studio language products, such as Visual C++®.

All they need is to tack on - and Visual FoxPro.

Those Microsoft VIPs are real bastards, terrible step parents and obviously could give a shit about the VFP community!! Two-faced bastards, I say. A simple mention of VFP in such a document would make suggesting a VFP solution a bit more exceptable. Why is Microsoft so afraid to give VFP any recognition?

Sorry for the ranting, I guess I need to get outside for a snowshoe. It's a beautiful sunny day here in Upstate NY. At least Microsoft doesn't control the weather because it would probably be raining wherever VFP developers roam.

>No. The revisions removed references to VC++ and VB being the only tools you should use to write COM middleware. Now it reads that all Visual Studio languages can be used. Still no specific mention of VFP and I doubt we'll see any.
>
>>I just revisited http://msdn.microsoft.com/vstudio/nextgen/webservices.asp and still no mention of FoxPro. Didn't I see a thread about this being revised to include FoxPro?