Hi Ken,

It´s great to reuse VFP code in the form of COM components but I feel frustrated every time I have to debug a VS.Net Solution and see that I can´t step on the vfp COM component code.

Visual FoxPro COM Debugging at VS.Net was a planned feature when VS.Net was in Beta 1 so I suppose that it´s feasible.

Why not offer the ability to debug vfp COM components as an "add on" to VS.Net? I believe that it would be a great enhancement in the development experience of those using Visual FoxPro COM components in VS.Net solutions and many Visual FoxPro developers would be interested in this "add on".

Eugênio

>>As you probably know, one cool way to use interop is with VFP web apps. Just call a vfp mtdll from ASP.NET. Then it's up to the developer to do more on the ASP.NEt side or not at their own rate...
>
>Yes, that one can be done since VFP 7.0 and VS.NET 2002. We have added improvements to XML support to/from ADO.NET in VFP 9.0. I'm mainly looking for feedback on what is missing for interop, for those VFP developers who are using or planning on using .NET with VFP together, like ASP.NET with VFP as you say, or mixing VFP forms and .NET WinForms, using VFP as a middle tier to .NET, or using .NET XML Web services via ASP.NET combined with VFP apps, etc.