Thanks for the honest and informative post. Care to take it to the next level and identify the VFP developers whom were pushing for the end of Fox? There are only a few big players in the VFP to .Net biz. Not that I would hold a grudge or avoid their services.

I was surpised by people posting that VFP is mature and does not need another version. Mostly surprised by the MVP's, I thought these were the guys with MS's ear and would be the ones pushing for the new features. I understand this as a rational why it is not the end of the world but I just do not buy that there was not enough requests pending to complile into a new version. One problem is any enhancement request is either excluded as to big (2gig, 64bit, cross-platform) or too small and not enough to warrent a new version.

I have been thinking about the CursorAdapter class. I did not know I wanted it before it was added, but now I use it constantly. A large part of it could have been created as an add-in class by the community but the portion of it that is build into the core VFP takes it from a good class to a great class. And I image the portions that are written in Fox like the builder are a lot more polished than they would have been if they had not become part of the MS VFP product.

Anyways thanks for the post, it was very informative.


>
>In the past, there have been numerous efforts to kill Visual FoxPro. And this is not just internal to Microsoft. I can recall discussions with prominent 3rd party VFP developers encouraging us to kill the product so that they might benefit (via .NET training, conversion tools, frameworks, etc.) from the exodus of VFP developers over to .NET products. When MS chose not to bring VFP over to .NET, for many that was the real strategic message on its future. I have read some recent blogs by friends indicating that the VFP product is mature and there really isn’t a need for new versions of the core executable. To some extent I agree (technically), however, if we get back to the business model, new versions provide incentive for clients to invest in new development efforts.