Look at the Interop Forms Toolkit at http://msdn2.microsoft.com/en-us/vbasic/aa701259.aspx. It says it's for VB, but it works for VFP. I'm in the process of rewriting the sample apps and help file for Microsoft to make them VFP applicable. Some of your questions are things I have on my list to look at, but haven't gotten to yet.


>We currently have a rather large VFP application that our team has been tasked to 'incrementally' migrate to .NET a form at a time! In other words: future releases will include more and more VFP forms that have been replaced with .NET forms. Is this even possible? I am certainly not a .NET guru and my concerns are:
>
>-The VFP application is SDI (all forms run in the _screen container) - how would I host a non-modal .NET form that would appear hosted without loosing the zorder when things like a VFP menu item are clicked?
>
>-How could I communicate between the VFP application and the .NET form? Would this be a time to use windows messaging, DDE, pipes, anything else?
>
>-Would each .NET form have to be a seperate EXE? Which of course leads to other questions such as resource usage and such.
>
>-Is there a 'best-practices' approach to things such as parameter passing?
>
>This is not a case of migrating business logic (ie com interop), but IDE integration. This will be a IDE morphing from VFP into .NET at the interface level over a period of time. Has anyone done anything like this before and if so please give me a clue where to start!
>
>Thanks,
>Troy