1

I have an application that interacts with another one, suspending it while not used. If I end the debugging abruptly the suspended process will stay alive in the background and needs to be terminated.

I did some research and looks like none of the people found a solution that is applicable to Visual Studio 2015, in particular the macro solution will not work since looks like a dropped feature since VS2010...

My current solution is to run the proper taskkill command as a post-build action and within the startup code of the program.

I'm looking for a more elegant way of killing it, so a "post-debug" event like the one portrayed by the macro below would be perfect:

Private Sub DebuggerEvents_OnEnterBreakMode(
   ByVal Reason As EnvDTE.dbgEventReason, 
   ByRef ExecutionAction As EnvDTE.dbgExecutionAction) Handles DebuggerEvents.OnEnterBreakMode
    If (Reason = dbgEventReason.dbgEventReasonStopDebugging) Then
        KillLeftoverProgram()
    End If
End Sub

So is there any way to execute a cleanup shell command after using the stop button?

Community
  • 1
  • 1
beppe9000
  • 1,018
  • 1
  • 13
  • 27

0 Answers0