>If you want to use .NET controls, you need to use Visual Studio .NET since VFP has its own controls and forms. We are looking into allowing VFP make calls directly to the .NET Framework from within VFP so you can instantiate .NET Framework or custom .NET classes and work with those object instances from within VFP. I'm researching the need and demand for this also, so if anyone has input they would like to provide for this type of ability, let me know (either here or email directly at klevy@microsoft.com).

Riiight. What seems would be 1000 times better would be if VFP wasn't using it's own controls and forms anymore and used the .NET controls. I mean allowing VFP to make calls directly to the .NET Framework from within VFP seems like a good idea - but as a developer I wouldnt waste my time - I'd just save myself the hassle and ditch VFP all together - which obviously I don't wanna do.....or give up on MS doing it and write my own flavor of foxpro that uses the .net IDE - which again I'm not excited about doing because it'd take me freakn forever.