>I think I know the answer to this but before I invest a lot of time in research, I wanted to ask here. Someone has surely gone down this path already.
>
>My company wants to port a piece of an existing VFP app to .NET. The piece consists of one form with several subsidiary forms, all with lots of code behind them. The idea is to recreate the forms in .NET and reuse as much of the supporting VFP code as possible. Is this feasible? First of all, is it possible to compile VFP code into a DLL that is callable from .NET? And if so, how do you deal with the fact that the code is full of VFP field names and VFP PEMs like .Value, .Refresh, and so on?
>
>Thanks in advance for any guidance.
>
>Mike
"is it possible to compile Visual FoxPro code into a DLL that is callable from .NET?" yes. But if I'm reading your purpose right the answer is no.
Check if this white paper answers better:
http://www.west-wind.com/presentations/VFPDOTNETiNTEROP/VFPDOTNETINTEROP.HTMCetin
