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?

>Hi All
>
>We have a large 10 old VFP application that is gradually being ported to .Net.
>A Big Bang re write is just not on the Cards.
>
>We want to use the VB Interop Toolkit 2.1 to start incorporating .Net components into our application.
>
>To all those devs with experience in using the VB Interop Toolkit with Visual Foxpro, have you had any instances where you had to abandon using the Interop Toolkit or where you had serious on going dificulties with the Interop Toolkit ?
>
>Should we even consider using the Interop Toolkit with our VFP application ?
>
>Do you know of any projects that have successfully used the Interop Toolkit ?
>
>Your comments would be most appreciated.