Profiling an outlook add-in

• 
  This post says that it should work, but the method described doesn't work for me.
  
  http://www.red-gate.com/MessageBoard/vi ... php?t=6354
  
  The profiler just keeps saying in the status bar "Launching Outlook.exe". I tried with all 4 profiling methods, and it's always the same result.

  jtalbot July 01, 2009 21:24

  - 0 +
• 
  Aah, interesting: the memory profiler works, but not the performance profiler.
  
  Note that I have to use the "launch ANTS x Profiler" from the visual studio menu; the "profile performance" and "profile memory" menu items are always disabled for the solution containing my outlook add-in. I'm using the trial version, and it was the same when I was usability testing with version 4.x.

  jtalbot July 01, 2009 21:31

  - 0 +
• 
  No reply -- does this just work for everyone else but me?

  jtalbot July 12, 2009 07:44

  - 0 +
• 
  Hello,
  
  You typically profile add-ins by profiling the process that launches them, in this case outlook.exe. If the status stays at "waiting", that's meant to indicate that the process being profiled did not load the .net runtime and may be all unmanaged code.
  
  I believe that the ANTS Profiler add-in only works with project types that produce executable output -- I don't believe it has the intelligence to go through the project's debugging properties and work out what process is meant to load the assembly.

  Brian Donahue July 13, 2009 12:31

  - 0 +

Add comment

Please sign in to leave a comment.