Hi,
I've developed a custom test adapter that works fine when running tests but has the following issue when trying to implement integrated debugging.
The test adapter does not execute the code itself but launches another application which does execute the test and reports results back via tcp sockets. The poblem is that when I launch the test using Test=>Debug=>All the debugger attaches to the vstest.executionengine.exe process but I don't see any way to attach my spawned process. I tried using IframeWorkHandle.LaunchProcessWithDebuggerAttached() however this always returns -1 and does nothing. The method is completely undocumented (Bing turned up no results).
So the question is: How do I suppress attaching to the execution engine and either launch my process under the debugger or attach to it (short of a DebugBreak in the process itself). How doesLaunchProcessWithDebuggerAttached() work? It looks like a noop.
Thanks,
Dave