Visual Studio Debug Engine Sample

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Mon, 13 Oct 2008 17:28:04 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008 as an administrator. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch. Several of the stopping events were being sent as synchronous stopping when they should have been asynchronous. The lastest update fixes that.

NEW POST: Can not show the arrow marker when the excution stop at the breakpoint.

simonwolf — Thu, 10 Jul 2008 08:50:49 GMT

After building it, I launch the sample debug engine through Tool/Project Launcher.

A minute later,
The callstack window shows the stack frame information----It is correct.
And the breakpoint window shows the breakpoints which I have set.------It is correct too.

However, in the source code window, the arrow marker does not show.

Then, If I type the local variant in the immediate window and type enter, The program will encounter a exception,
The exception is "Unhandled exception at 0x3f25236e in devenv.exe: 0xC0000005: Access violation reading location 0x00000000"

The function which cause this exception is HeapSize in Visual Studio 9.0/VC/crt./src/msize.c, line:88.

Is there any hint to solve this bug?

------------------------
BTW, The sample works well in my college PC.

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Mon, 09 Jun 2008 21:53:02 GMT

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 06 Jun 2008 00:28:41 GMT

NEW POST: Can't launch

sgraham — Wed, 21 May 2008 23:50:42 GMT

Just a follow up, dbg.LaunchDebugTargets is returning 0x89710016.

The only relevant information I could find is http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1234362&SiteID=1 but unfortunately, that doesn't solve the problem (with VS 2008, the CLSID is in Wow6432 already). Does seem like the problem is probably x64 related though, I guess.

Also tried starting the subprocess (undebugged) rather than using the addin Launcher, and then Attach to Process'ing from VS, but no better:

---------------------------
Microsoft Visual Studio
---------------------------
Unable to attach to the process. The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger.

:(

NEW POST: Can't launch

sgraham — Wed, 21 May 2008 21:42:36 GMT

Hi

I'm just trying to get started with this sample but I'm unable to get it to launch. Using the ProjectLauncher addin does nothing visible (after choosing the project and clicking Launch). It seems slightly worse than the previous release, which appeared to launch, but then crashed right away in the UNLOADDLLDEBUG_EVENT case in WorkerAPI.cpp.

I also tried attaching from a __debugbreak()'d test, and selecting "Manually choose the debugging engines". "Sample Debug Engine" appears in that list, but VS says:

---------
Process: x.exe
The requested attach was not completely successful.

Successfully attached these type(s) of code:
Native

Failed to attach to these type(s) of code:
Sample Debug Engine: The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger.
---------

Any suggestions?

Thanks,
Scott
(Vista x64 in case that matters)

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Tue, 20 May 2008 18:22:01 GMT

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Tue, 20 May 2008 18:21:30 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch. Several of the stopping events were being sent as synchronous stopping when they should have been asynchronous. The lastest update fixes that.

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 29 Feb 2008 01:59:49 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch. Several of the stopping events were being sent as synchronous stopping when they should have been asynchronous. The lastest update fixes that.

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 29 Feb 2008 01:59:14 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch. Several of the stopping events were being sent as synchronous stopping when they should have been asynchronous. The lastest update fixes that.

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 29 Feb 2008 01:58:26 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Thu, 28 Feb 2008 23:02:34 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Mon, 25 Feb 2008 23:53:38 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Mon, 25 Feb 2008 22:48:21 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Mon, 25 Feb 2008 18:01:48 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Sat, 23 Feb 2008 03:57:38 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This release fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Sat, 23 Feb 2008 00:23:32 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This releases fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 22 Feb 2008 23:56:02 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This releases fixes some issues with the self-registration and resolves a race condition during process launch

CREATED RELEASE: Debug Engine Sample v1.1 (Feb 22, 2008)

Fri, 22 Feb 2008 20:58:03 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.

This releases fixes some issues with the self-registration and resolves a race condition during process launch

UPDATED RELEASE: Debug Engine Sample v1 (Feb 20, 2008)

Thu, 21 Feb 2008 21:26:39 GMT

The debug engine sample is contained within this zip file. The solution contains the managed front end (written in C#), the mixed mode C++ backend, and the project launcher to demonstrate the launch scenarios. To use the sample, download the zip file to your machine and decompress it. Open the solution in Visual Studio 2008. Build the sample and run it. Visual Studio should open under the debugger. Open a Visual C++ project in the new instance of Visual Studio, build it, and then go to the project launcher tab under the tools menu. A form should open that shows the name of your project. Choose launch on the form and the VC++ project should launch under the sample debug engine.

NOTE: if you are not running Vista, you will need to modify the addins path in the project launcher project from %usersproflie%\username\documents\visual studio 2008\addins to %usersproflie%\username\my documents\visual studio 2008\addins because of the change in the name of the my documents folder.

The sample is split into three separate projects:
1) A front end implemented in C# which implements the AD7 interfaces and interacts with the SDM. The root object of this project is AD7Engine which implements IDebugEngine2. This project is called Microsoft.VisualStudio.Debugger.SampleEngine.
2) A back end implemented in mixed mode C++ which interacts with the win32 debugging API and DIA, the public symbol interfaces. This project is called Microsoft.VisualStudio.Debugger.SampleEngineWorker.
3) A Visual Studio Addin which is used to launch Visual C++ projects using the new engine. This project is named ProjectLauncher. It adds a new command button “ProjectLauncher” to the Visual Studio Tools menu which will launch a form that displays the current projects in Visual Studio that can be launched with the new engine.