>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.

Well, what you're basically asking for then is VFP.Net which as far as I know was decided against a long time ago by Microsoft and also most developers.

And I would agree that this would not anything all that useful.

My question to you is why would you want to do this? If you need to call Fox code today from .Net you can do that. If you need to call .Net code from VFP today you can do that. WHat else could you really want then short of a full .Net version of VFP?