I sent a similar letter to other folks there. Good one, David. To me this is a critical issue, as they have been blowing smoke up our ass for 12-18 months about VFP as middleware and this omission is "fightin' words" IMHO.


>Here is what I just sent to Robert Green and Randy Brown. I'm awaiting their response.
>
>Hey Robert and Randy,
>
>The new Visual Studio 7 announcement contains some very exciting new developments. I am looking forward to the VFP7 Beta to work with the new web-oriented features of VS, such as Web Forms and Web Services.
>
>However, I'm appalled that the first official announcement makes ZERO mention of VFP, and instead urges developers to build middle-tier components in VB or VC. (It is encouraging to see "Visual Foxpro Projects" in the project manager).
>
>From 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.
>
>"ALL the language products..." sounds promising, but then NO mention of VFP, leaving the general IS public to conclude once again that VFP is LEGACY ONLY and NOT RECOMMENDED.
>
>Can be created with any tool supported in Visual Studio, including Visual Basic and Visual C++.
>
>"ANY TOOL", then just VB & C++.
>
>Then, the most outrageous of all:
>
>To prepare for using Web Forms, we recommend that you build your application on a multi-tier architecture. The core business functionality should be placed in middle-tier components authored in Visual Basic or Visual C++.
>
>WHY?
>
>WHY?
>
>WHY?
>
>Should I forward my marketing concerns to SteveB and BillG, or what? I await your response.
>
>David Stevenson, MCP Visual Foxpro
>dsharpie@mindspring.com