visual studio code debugger attach process

returnprocesses.SingleOrDefault(x => x.ProcessID = processID).

var dte = (DTE) Marshal.GetActiveObject( 'VisualStudio.DTE.12.0' ).

private static Process GetProcess(intprocessID).

Console.WriteLine( 'Attached to ' , process.Name).public static void ToProcess(intprocessId).private static extern intCoRegisterMessageFilter(IOleMessageFilternewFilter, outIOleMessageFilteroldFilter).CoRegisterMessageFilter(newFilter, out oldFilter).private static void CoRegisterMessageFilter(IOleMessageFilternewFilter).CoRegisterMessageFilter(newMessageFilter()).int IOleMessageFilter.MessagePending(IntPtrhTaskCallee, intdwTickCount, intdwPendingType).returndwRejectType = RetryAllowed ? Retry : Cancel.int IOleMessageFilter.RetryRejectedCall(IntPtrhTaskCallee, intdwTickCount, intdwRejectType).int IOleMessageFilter.HandleInComingCall(intdwCallType, IntPtrhTaskCaller, intdwTickCount, IntPtrlpInterfaceInfo).public class MessageFilter: IOleMessageFilter.int MessagePending(IntPtrhTaskCallee, intdwTickCount, intdwPendingType).int RetryRejectedCall(IntPtrhTaskCallee, intdwTickCount, intdwRejectType).int HandleInComingCall(intdwCallType, IntPtrhTaskCaller, intdwTickCount, IntPtrlpInterfaceInfo).I have done a little customization to get the process Id as argument: Then I found this SO post and it really worked amazingly. I found a VS Addin from Visual studio team to attach child process automatically to current debugger but it seems it only works with 'F5' debugging. Now, comes the part to attach this process for debugging. ViewrawWCFDynamicProxyTest.cs hosted with ❤ by GitHub Assert.IsNotEmpty(result, 'The result was empty.' ).Assert.IsNotNull(result, 'The result was null.' ).var proxy = DynamicProxyWrapperFactory.GetProxyInstanceByInterface ( 'TestService' ).public void GetDefaultWCFClientProxy_RequestingProx圜lientGeneration_Succeeds()./// Case when the method GetDefaultErrorLoggingInterfaceProxy was invoked to get the real.

ServiceHostProcessInvoker.KillDummyService().

/// Tear down to perform clean when the execution is finished.

ServiceHostProcessInvoker.InvokeDummyService().

/// Setup required before the tests of the fixture will run.

public class CustomClientProxyFactoryTest.

/// as we're testing it on dummy service client.

/// Implements the tests for CustomClientProxyFactory class. The tests have falvour of integration.

Then completion of test just kill the process. In this Test I’ll be invoking a Dummy service instance hosted in a Console application. Here the Integration test is a sample from one of my Github project WCFDynamicProxy. Now in the TestInitialize and TestCleanup methods (I’m using NUnit in this sample code so it would be TestFixtureSetup and TextFixtureTearDown methods) I would start the process and kill the respective process. ViewrawProcessInvoker.cs hosted with ❤ by GitHub

Process.GetProcessesByName( 'DummyService' ).ToList().ForEach(x => x.Kill()).// This is what would attach the process to current VS debugger.ProcessStartInfo info = newProcessStartInfo(Path.Combine(path, 'DummyService.exe' )).var path = Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location).public static void InvokeDummyService()./// Invokes the host process for test service.

Visual studio code debugger attach process