>Actually I'm quite pleased that you've got this new job title - at least it means that the VFP community's voice will be heard in the right places. Quite why some people here are getting so caught up in the meaning of a job title I don't know. Perhaps no one else has any work to do.
>
>My concern is more that you won't come out and say quite simply: VFP will work with Longhorn in a future version. Leaving us dangling in mid air with no clear commitment is more damaging than saying something then retracting it later. If the .NET people can say that, why can't the VFP team also say it?

I had said that while VFP will work on Longhorn like any Win32 COM based application, it will not be designed to build Longhorn-specific applications using new technologies sucn as the Windows .NET Framework, WinFX/WinFS, Indigo, Yukon, XAML (Avalon), etc.