VS 2010 version of DebugEngineSample is now available

The Debug engine sample available at http://code.msdn.microsoft.com/debugenginesample has been updated for VS 2010. Changes include porting to use Microsoft.VisualStudio.Debugger.InteropA.dll as the primary PIA, updating registration to load in VS 2010 and implementing a few new interfaces for VS 2010.

NOTE: All debug engines implemented in managed code must switch to using Microsoft.VisualStudio.Debugger.InteropA.dll as the pia for AD7. This is an unfortunate side-effect of adding managed code to the debugger UI. The problem is the com interfaces defined in old pia (Microsoft.VisualStudio.Debugger.Interop.dll) are treated as different types by the CLR then those defined in InteropA. The end result is the debugger UI will no longer be able to talk to engines that use the old deprecated PIA.

Comments (2)

  1. tgraupmann says:

    The documentation walkthroughs still reference VS 2008. I also get a compile error:

    1>  Does C:UserstgraupmannDocumentsVisual Studio 2010Addins specify a file name

    1>  or directory name on the target

    1>  (F = file, D = directory)? ?

    So I manually made that folder. It could be a prebuild step. And the project compiles successfully.

    How would a person debug the debug Add-In? You have a separate VS instance to compile the Add-In. And you use the Tools menu item to launch the custom debugger. If I wanted to set a breakpoint in the Add-in for the debugger connect event, how would you go about that?

  2. tgraupmann says:

    I see the breakpoints can be hit if you are debugging a specific type of application.

    What if I wanted to attach the debugger to chrome or firefox? What controls what types of applications your sample plugin can connect to?

Skip to main content