Click here to Skip to main content
11,503,151 members (78,412 online)
Click here to Skip to main content

Automate the "attach to process"

, 25 Oct 2013 CPOL 23.1K 516 34
Rate this:
Please Sign up or sign in to vote.
Automating the Attach to Process from within Visual Studio.

Introduction

Often you can catch yourself doing repetitive work. Sometimes I even manage to get annoyed before I realize what the problem is. This article is about my latest idea: automating the "attach to process" from Visual Studio.

Background

Developing a client/server solution will often bring you in a situation where you start debugging the client and then realize that there is a problem with the server, so you start the client (again) and attach Visual Studio to the server in order to debug the problem. After a while, this routine becomes really annoying. While reading through some of the Microsoft pages regarding EnvDTE, I had an idea. The idea is basically to get hold of the running instance of Visual Studio from the client and use EvnDTE to attach to the server.

Using the Code

I created an extension method to extend the System.Diagnostics.Process. This seemed rational since I had to use a Process to start the server from the client.

The code is as follows:

public static void Attach(this System.Diagnostics.Process process)
{
  // Reference Visual Studio core
  DTE dte;
  try
  {
    dte = (DTE) Marshal.GetActiveObject(progId); 
  } catch (COMException) {
    Debug.WriteLine(String.Format(@"Visual studio not found."));
    return;
  }
  
  // Try loop - Visual Studio may not respond the first time.
  int tryCount = 5;
  while (tryCount-- > 0)
  {
    try
    {
      Processes processes = dte.Debugger.LocalProcesses;
      foreach (Process proc in processes.Cast<Process>().Where(
        proc => proc.Name.IndexOf(process.ProcessName) != -1))
      {
        proc.Attach();
        Debug.WriteLine(String.Format
		("Attached to process {0} successfully.", process.ProcessName));
        break;
      }
      break;
    }
    catch (COMException)
    {
      System.Threading.Thread.Sleep(1000);
    }
  }
}

Using the extension method can be done like this (example):

Process p = new Process();
FileInfo path = new FileInfo(Assembly.GetExecutingAssembly().Location);
string pathToProcessToDebug = Path.Combine
    (path.Directory.FullName, @"..\..\..\ProcessToDebug\Bin\Debug\ProcessToDebug.exe");
ProcessStartInfo psi = new ProcessStartInfo(pathToProcessToDebug);
p.StartInfo = psi;
p.Start()
p.Attach(); // <-- Extension method 

Points of Interest

The idea could be implemented in any number of ways, but I was keen on using an extension method. I looked at the System.Diagnistics.Debug class for an appropriate place to add the method - but static classes cannot be extended.

History

  • Version 1.0 (First version).

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Niel M.Thomas
Architect
Denmark Denmark
Name: Niel Morgan Thomas
Born: 1970 in Denmark
Education:
Dataengineer from Odense Technical University.
More than 20 years in IT-business.
Current employment:
Working with application development in a major Danish company that produce medical equipment.

Comments and Discussions

 
Questionwhat is progId Pin
vikas.yerram22-Nov-14 19:32
professionalvikas.yerram22-Nov-14 19:32 
AnswerRe: what is progId Pin
Niel M.Thomas22-Nov-14 21:23
professionalNiel M.Thomas22-Nov-14 21:23 
GeneralRe: what is progId Pin
vikas.yerram23-Nov-14 15:59
professionalvikas.yerram23-Nov-14 15:59 
QuestionCould any one tell me the simplest step to use it? Pin
leiyangge16-Jan-14 4:30
memberleiyangge16-Jan-14 4:30 
AnswerRe: Could any one tell me the simplest step to use it? Pin
Niel M.Thomas16-Jan-14 4:35
memberNiel M.Thomas16-Jan-14 4:35 
GeneralRe: Could any one tell me the simplest step to use it? Pin
leiyangge16-Jan-14 14:32
memberleiyangge16-Jan-14 14:32 
QuestionThis may help too Pin
Mauro Leggieri5-Oct-11 15:19
memberMauro Leggieri5-Oct-11 15:19 
GeneralMy vote of 5 Pin
ShdNx4-Oct-11 5:03
memberShdNx4-Oct-11 5:03 
GeneralMy vote of 5 Pin
GPUToaster™3-Oct-11 23:22
memberGPUToaster™3-Oct-11 23:22 
GeneralMy vote of 5 Pin
HoyaSaxa9330-Sep-11 10:43
memberHoyaSaxa9330-Sep-11 10:43 
GeneralRe: My vote of 5 Pin
kiran dangar4-Oct-11 0:36
memberkiran dangar4-Oct-11 0:36 
QuestionImpeccable timing guys Pin
rocware2129-Sep-11 13:25
memberrocware2129-Sep-11 13:25 
Suggestionseems a bit excessive to me Pin
Blkbam29-Sep-11 7:19
memberBlkbam29-Sep-11 7:19 
I have a macro that I use in the same way but I don't start the process in my macro. I use the code below:
    Public Sub AttachToProgram()
        Dim process As EnvDTE.Process
 
        For Each process In DTE.Debugger.LocalProcesses
            If (Path.GetFileName(process.Name).ToLower() = "program.exe") Then
                process.Attach()
                Exit Sub
            End If
        Next
 
        MsgBox("program.exe process not found")
    End Sub

This of course could be modified to either accept a process name and be more dynamic or to even start the process itself. I'm not too comfortable with the multiple loops you have there. Even this one here adds a slight lag with only one pass of a loop.
GeneralRe: seems a bit excessive to me Pin
Niel M.Thomas29-Sep-11 8:08
memberNiel M.Thomas29-Sep-11 8:08 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.150520.1 | Last Updated 25 Oct 2013
Article Copyright 2011 by Niel M.Thomas
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid