But you don't need the VB interop toolkit for that, at least not to pass and receive data from a .net dll in VFP or fire events in VFP from .net. We do that now via com interop...

>The VB Interop Toolkit definately works with VFP. But you don't need it for ActiveX controls as they "just work" on a VFP form. What the toolkit does is allow you to call VFP code from .NET and vice-versa and even have events in one environment fire code in the other.
>
>>Hi Jared,
>>
>>I have not used the VB Interop Toolkit, but my understanding is that it is supposed to work with VFP. If you're wanting to put .NET components on a VFP form (like an ActiveX control), then I think it is your only option. Otherwise, I would steer you towards wwDotNetBridge, which gives you more complete access to the .NET framework without COM wrappers. I believe it will let you open a .NET form in VFP, but you'll want to double-check on that:
>>
>>http://www.west-wind.com/webconnection/wwClient_docs/_24n1cfw3a.htm
>>http://www.west-wind.com/wwClientTools.asp
>>
>>As Tracy said, you could make .NET the host environment for your UI and put VFP code in a COM object. That may be a better choice if you'll be rewriting your entire UI at once. You can host a VFP form in .NET using the SetParent() API, but that's kind of a hack. It depends on who you want to do the driving.
>>
>>By the way, what will you be using for the new UI: Winforms, WPF, or SilverLight?