>In my opinion, seeing as .NET is becomming more and more mainstream, a very important feature for future versions/updates of VFP, will be improved interop with .NET.
>
>For example, a way to use .NET winforms more or less seamlessly inside a fox application would be great. I know that this is "sort of" possible today using COM interop and a bunch of double loops in .NET, but a clear, consistent way of doing this would be nice. For example, a .NET form should behave like a proper fox form, and not always stay on top, etc.
>
>I am sure you guys can think of mayny other great ways to improve interop as well.

We do want to continue to enhance interop. But in some cases you are talking about merging, like with the .NET WinForm inside VFP behaving like VFP, and in some cases that won't occur. But this feedback is good, so keep it coming. If you have other specific ideas and needs around VFP with .NET interop, please let me know. What I need is very specific features and functionality backed by scenarios that explain why it is needed. I took note of your scenario above with the WinForm to research that, thanks.