Clearly - VFP is not dead. I was wrong. Ken's latest actions to get the case study corrected finally put to rest MS's ambivalence toward Fox. It is a new day indeed.
As I just said in another post = you won't hear me or see me saying Fox is dead nor will I advocate people eschew it in favor of .NET.
I was wrong - that is about all I can say on it.
><snip>
>>I see your point. But....this is the first case study from MS which essentially endorses the notion of actively replacing Fox apps with .NET.
>
>hmmm, the following postings by no less an authority on VFP than Ken Levy certainly appear to take the wind out of that statement:
>
>
Re: New case study in MSDN Flash Thread #
856811 Message #
858354>
Re: New case study in MSDN Flash Thread #
856811 Message #
858358>
Re: Can We Buy Visual FoxPro Source Code?? Thread #
857636 Message #
858357>
Re: Can We Buy Visual FoxPro Source Code?? Thread #
857636 Message #
858356>
>I cant help wondering, John, that if your statement above and the "VFP is dead" gang are correct why after VFP6 was there a VFP7, VFP7/SP1, VFP8, VFP8/SP1, VFP9 under development, redesign and development of the VFP homepage, and greater exposure of VFP on MSDN. Plus support for VFP8 until 2010 which will possibly be extended when VFP9 is released.
>
>If MS want VFP to be replaced why continue to buld new versions? When you want to drop a product line surely the first step is to stop developing it? The fastest way for MS to drop VFP is to first and foremost stop enhancing it at all. You will of course argue that the enhancments are not major but this is an opinion and I think some of the enhancments are fantastic. And even if they are not major why do them at all?