It looks like a pretty good tool. I cant easily read the documentation and have to view the source and past and edit the html to get a readable copy of the CHM (most topics in the CHM are in a unscrollable edit region).

Anyway - following their example in building a .NET form on the fly does work pretty good, but looses the zorder when interacting with the VFP application. In other words, clicking on the VFP menu puts the .NET form behind VFP. I was hoping the .NET form would be hosted in the VFP MDI and even honor its boundaries. Since the trial only give me 30 minutes of 'play' time I can't spend a lot of time exploring.


>Hi:
>
>There is two options:
>
>1. Make the form´s class public and use
>SetCLRClassLibrary("the path/to your/assembly.dll",.T.)
>oForm = CLRCreateObject("yournamespace::YourClassName").
>oForm.Show()
>
>
>2. Make the form look like a Control (no ControlBox and not caption) and put it in a VFP Form using netbasecontrol (in netbasecontrols.vcx). Remember to se cControlClass to "yournamespace::YourClassName".
>Allways is needed to call:
>SetCLRClassLibrary("the path/to your/assembly.dll",.T.)
>
>I hope this help you
>
>Martin