If you're debugging from within ASP or ASP.NET you should let VFP start up a new copy each time because that's what happens with a DLL server. If you truly want to debug your code you should try to simulate the same exact environment that the COM server is running through or otherwise you'll see inconsistent behavior.

IAC, that process is fraught with all sort of issues such as how much data you can pass around (because you have to pass parameters as literals). It's better than nothing (well maybe it isn't <s>)...

Don't throw out the old the LogToFile() (or like) routine just yet <s>...

+++ Rick ---

>Hi,
>
>I am implementing a com server to provide access to VFP code from .NET based on articles by Calvin Hsia and Rick Strahl
>
>http://blogs.msdn.com/calvin_hsia/archive/2007/05/21/write-fox-code-in-visual-studio-that-interacts-with-your-vb-net-code.aspx
>
>http://www.west-wind.com/presentations/VFPDOTNETiNTEROP/VFPDOTNETINTEROP.HTM#Debugging%20your%20COM%20server
>
>It has come to the point that SET STEP ON opens the VFP debugger, but each time I run my test code I create a new copy of VFP. I'd like to change the code to use an already running copy if available. In Rick's article there is a reference to another article, by Maurice de Beijer who provided the original idea, but it depends on storing the hwnd value of the design time VFP on disk.
>
>http://www.theproblemsolver.nl/aspdevelopmentanddebugging/index.htm
>
>I wonder if there is some way to cycle through all windows and pick it up automatically, perhaps knowing the title or some other trick.
>
>TIA,
>
>Alex