>Several of you have wondered about this statement on the Web Forms page on MSDN (http://msdn.microsoft.com/vstudio/nextgen/webforms.asp)
>
>"In the next release of Visual Studio, all the language products share the same Web technologies. Regardless of whether you choose Visual Basic or Visual C++®, the product functionality is the same. Therefore, you can choose your favorite language to build Web Forms further increasing productivity."
>
>Where is VFP you ask? Web Forms are a User Interface designer and we can't at this time make a blanket promise that VFP will have the same functionality as VB and VC for Web Forms, or for Windows forms for that matter. We will do what we can, but it is too early to say what that will be.

Thanks for letting us know that you are attempting it.

>I can guarantee that you will be able to make great Web Services in VFP, just as you can make great COM components today. You can think of Web Services as components that run on the Web, not just on a network. They take in XML, they do some work, they return XML. And VFP will have great support for building and consuming Web Services.

So, how about adding "and Visual Foxpro" to this statement on the Web Services page:

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++® and Visual Foxpro.

Looks a little more accurate to me.

>Hope this clarifies things a bit.

Thanks.