If you're trying to load Windows Forms it'll likely fail due to the lack of a separate message loop for the Windows Forms application. It seems to work but there are all sorts of glitches and likely hard crashes that'll occur do to the threading problems.

You can use modal windows forms (form.ShowDialog()) and that works very well because it doesn't require a separate message loop as it suspends the FoxPro message loop. There are ways to make non-modal forms work but it requires spinning up a new thread and running the form off of its own separate STA message loop. Even then I seem to remember it wasn't super stable and frankly if you do that you might as well compile the forms into a EXE and launch that instead - when the main form closes the window closes :-)

+++ Rick ---

>>Hi everybody, there's a new open source .Net interop library for VFP
>>called "kodnet" similar to wwDotnetBridge.
>>
>>The author claims it has advantages over it, but I have not tested
>>kodnet -nor ww.DotNetbridge!- , so it would be interesting if folks who
>>are familiar with .net interop could take a look and share with
>>us their findings.
>>
>>site: https://github.com/voxsoftware/kodnet
>
>Thanks for sharing. All samples are working fine for me.
>
>One thing I tried was a simple form that I created and I was surprised by the errors I got. Probably forms are not supported at all.