>Another suggestion. I found it a bit sad that you guys don't really work on improving the IDE. Unless I did'nt understant this part in the newsletter. Is that really a closed subject for your team?

Our focus and resources are going into enhancing VFP for interoperabiilty, not the core VFP product beyond what is needed to enhance and deliver on the interop story. Leveraging the .NET Framework, features for running VFP apps on Longhorn, being able to call Avalon forms from VFP, working with SQL Server and Office better, etc. are all a higher priority than adding new features to the grid and other controls, etc. We will enhance many of the IDE features in VFP via extensiblity. Lots can be done here, more than some might expect or imagine. That includes new DLLs written in C++ and not just Xbase (FoxPro) code.

>The reason is that I go to monthly meetings and when they show stuff with .Net some of the things in the editor are really cool.

Yeah, and the time and effort (costs) of adding IDE things to VFP is not as important has how VFP apps deploy (the end user experience). The runtime (end result) is what is more important than nice features. Keep in mind that the VFP team now (and with VFP 9.0) is under 10 people while people working on VS 2005 and the .NET Framework is well over 1000.

I will continue working on answering questions like this and commenting on various suggetsions as direct and as honest as I can. I don't think there has been one question on the UT today that I haven't answered directly or avoided. While we always like to keep our options open and also avoid stating formally things we will not be doing, we want to be more open than ever about what our plans are, why, and what to expect.