locked
Visual Studio Custom Test Adapter debugging issue RRS feed

  • Question

  • 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

    Friday, November 8, 2013 11:56 PM

Answers

  • Hi Dave,

    I have searched about "LaunchProcessWithDebuggerAttached()" and find nothing. Could you please provide us with that? 

    However, you can read "Implementing Traits in custom Visual Studio Test Adapters" and "Authoring a new Visual studio unit test adapter" . They can help you a lot. If you still have any questions, please feel free to let me know.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.




    • Edited by Anna Cc Thursday, November 21, 2013 3:56 AM
    • Marked as answer by Anna Cc Thursday, November 21, 2013 3:56 AM
    Monday, November 11, 2013 9:08 AM