Hi Jim,
>I think there is some confusion with the newsgroups that are referenced there. VFP was originally in VS .Net and available in Beta 1. It was pulled after that due to requests from the VFP Community.
I think Craig may be talking about some that took place at that time and perhaps had some influence on MS decision. Please check
http://fox.wikis.com/wc.dll?Wiki~ShouldVFPBeInVSDotNet~VFP, specifically about what Robert Green said (here in the UT) and was posted there at the wiki:
"To be perfectly honest with you, our ability to do that (market VFP on its strengths) is greater if VFP is not in the VS box. If VFP is in VS, it has to have a VS story. In 6.0 that meant middle tier and DNA. In VS.NET that means the next generation of Web apps. If VFP is not in VS, then we can have our own story, which means we can go back to bragging about the things that Fox does best."If I'm not wrong that page was started by Mike Feltman (
"I recently had the opportunity to discuss whether or not Visual FoxPro should be included with Visual Studio.NET or made a standalone product again with some of the members of the Fox Team at Microsoft. The Fox Team is very interested in hearing what the community thinks about this. The following is my opinion on the subject. It doesn't necessarily represent the Fox team's opinion..."Hope this helps,
Fernando