>Attended Microsoft's code camp in Philadelphia over the weekend. It was an excellent mini-conference with sessions by many of the bigger names in .net.
>
>One session dealt with the new stuff in VS2005 and the group was ooo'ing and ahhhh'ing over things like the intermediate window (analogous to the command window but way less powerful) and the ability to edit values and continue debugging with the new values.
>
>You should have seen the look on their faces when I piped up and said, "VFP has had that ability for years."
>
>You could have heard a pin drop. I thought it was funnier than anything. The presenter looked at me, and just said "Oh."....
>
>BTW, our Kevin Goff, MVP Extraordinaire, presented two sessions that were really well received. Good job Kevin!

There is more than just what you list in VS 2005 taken from VFP. For example, the team that designed the form/controls databinding (like dragging from data sources onto a form for a grid or set of controls) actually had VFP 8.0 installed on their machines for design review. Expect to see more of this ongoing, per the VFP FAQ at http://msdn.microsoft.com/vfoxpro/productinfo/faq/default.aspx

Q: What is Microsoft's position on Visual FoxPro related to Visual Studio and .NET?
A: We do not have plans to merge Visual FoxPro into Visual Studio and .NET, and there are no plans to create any sort of new Visual FoxPro .NET language. Instead, we are working on adding many of the great features found in Visual FoxPro into upcoming versions of Visual Studio, just like we've added great Visual Studio features into Visual FoxPro. If you want to do .NET programming, you should choose a .NET language with Visual Studio.