>>I am working with an application that includes both VFP and CS.NET components. In some cases CS.NET programs instantiate VFP classes that are built as Interop DLLs. The .NET programs are able to call and use the classes with no trouble. Is there a way, though, to debug code in the VFP class? I can do so to an extent by instantiating the class from the VFP command window and then running it there, i.e. oMyClass.MyMethod(). Unfortunately the class was written with some dependencies on other things in the .NET app so it's kind of a pain to do it that way. I would like to invoke it from the .NET app and then use the VFP debugger to step through methods.
>
>It's not pretty but I seem to remember using this in the past:
>http://www.levelextreme.com/ViewPageArticle.aspx?Session=3930634D5031794A7770493D20474545556C58754642626842782B47554450747031413D3D

Thanks, Viv. The first half of the article is pretty grim -- basically describing the exact issues I was running into -- but maybe there is some hope in the solution described in the second half. An imperfect tool is better than no tool at all.

Has Microsoft processed your MVP award yet? <g> That's a smiley but I am not really joking. This is long overdue and I am not going to shut up about it until they fork it over <g>.