Hi Craig,

I did read about MS's strategy to pull VFP out of the .NET framework. You mentioned that a majority of people did not want it to be in the .NET framework in DevCon. I would be interested to know the some of the reasons given for keeping VFP out, if for nothing, just to argue the case that MS has interest in keeping VFP alive beyond .NET.

It does seem till now, that in most MS releases, KB articles etc, they always refer to '...any development language which can create COM objects like VC++, VB ...' and leave VFP out. And that's what doubting thomases are always touting.


Thanks,


Sanjay

>I know that MS saw the lists. I periodically sent the list to the VFP team. I also know they looked at it from time to time.
>
>As to your worry of "does the team listen to us", I guarantee they do. At DevCon last year in Miami there was lots of discussion with the team on what features we would and wouldn't like to see. Many of the things discussed made it into VFP7. THe biggest topic revolved around inclusion in VS.Net. The majority of people there did not want it...hence VFP was pulled from VS.