Hi Ken,

I appreciate what you are saying about the plan. I also seem to remember that Coram's Boyd book was the rage in Redmond last year. If so, there's hope that the concept of maintaining accelleration in a curve can gain some traction.

Hank

>Hi Hank. The topic of Microsoft adding some kind of VFP.NET language .NET based CLR compiling is more of an issue of what resources and strategy rather than an issue of ability or possibility. The efforts for Visual FoxPro at Microsoft are on the Sedna add-on interop and extensibility project as well as an upcoming SP2 for next year. Beyond that, any resources that could be for VFP are being re-directed to add VFP features to .NET programming such as VB and C#, including the new LINQ project.
>
>Rather than putting resources into something like IronPython towards a VFP.NET like language, all efforts and resources will be on people working on adding more data-centric and other VFP like features to VB, C#, and the VS IDE. This is the plan from the top down, has been for a long time. The plan is in place, it is documented at http://msdn.com/vfoxpro/roadmap, and you shouldn't expect the plans related to VFP (the VFP product or how VFP relates to .NET) to change from that publicly documented plan. The primary feedback that is going to have an impact on what is done related to VFP is feedback within the context of the existing VFP Roadmap as well as feedback on the existing features and scenarios of the Sedna project (CTPs, specifications, samples, etc.
>
>So while the VFP team is always open to feedback, being realistic means feedback that relates directly to Sedna and within the scope of the VFP roadmap outline.