We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

Visual Studio Debugger Extensibility

Updated: April 2011

Microsoft Visual Studio 2010 includes a fully interactive source code debugger, which provides a powerful tool for finding bugs in your program. The debugger has complete support for the Visual Basic, Visual C#, and C/C++ languages, in addition to the scripting languages ECMA, VBScript and JScript. However, with the Visual Studio SDK that is available from the Microsoft Download Center, additional computer languages can have the same level of support in the debugger.

The Visual Studio debugger is the common front end, that is, the user interface, for the debugging components that are specific to the language being debugged. For new languages, all that is required for support by the Visual Studio debugger is to create the necessary back-end components, such as a debug engine (DE). That is where the Visual Studio SDK is useful.

The Visual Studio SDK includes a complete reference to all Visual Studio elements that are required to create a new DE. In addition, there are samples and tutorials that will help you get started.

For an end-to-end sample of a language project system with debugging support, see the IronPython sample.

The following sections describe how to extend the debugger by using the Visual Studio SDK.

Getting Started with Debugger Extensibility

Describes what Visual Studio Debugging offers and how to install the SDK.

Creating a Custom Debug Engine

Documents the custom DE process, from preparing your program for a DE to detaching the DE.

Writing a Common Language Runtime Expression Evaluator

Explains whether you must write an expression evaluator.

Choosing a Debug Engine Implementation Strategy

Discusses how to implement your DE.

Reference (Visual Studio Debugging APIs)

Documents the Visual Studio Debugging API.

Visual Studio Debugging Samples

Contains links to a common language runtime expression evaluator sample and a debug engine sample.

Date

History

Reason

April 2011

Removed licensing restrictions

Information enhancement.

Show: