-
Notifications
You must be signed in to change notification settings - Fork 51
Overview
Patrick Nelson edited this page Dec 6, 2016
·
3 revisions
Concord is the code name of Visual Studio's new debug engine that originally shipped in Visual Studio 2012. The basic design of Concord is a collection of many modular, self-contained components working together to form the debug engine. Concord is extensible and new components can be added to enable debugging different languages, different runtimes, or to add new features to the debugger.
These components communicate through a special API. This API greatly simplifies the task of writing components and integrating them. Here are some features of the Concord API:
- Supports transparent managed/native marshalling enabling components to be written in either managed or native code.
- Handles the complexity of communication between the IDE process and the remote debugger process (msvsmon).
- The API itself is available as part of the Visual Studio SDK enabling anyone to write new components.
Concord Documentation:
- Overview
- Visual Studio 2022 support
- Concord Architecture
- Getting troubleshooting logs
- Tips for debugging extensions
- Component Discovery and Configuration
- Component Levels
- Navigating the Concord API
- Obtaining the Concord API headers, libraries, etc
- Concord Threading Model
- Data Container API
- Creating and Closing Objects
- Expression Evaluators (EEs)
- .NET language EEs
- Native language EEs
- Installing Extensions
- Cross Platform and VS Code scenarios:
- Implementing components in native code:
- Worker Process Remoting
Samples: