Scenario

In addition to powering native (C/C++) debugging in Visual Studio, Concord also can be used in VS Code with the cppvsdbg debug adapter from the C/C++ VS Code Extension starting with C++ extension release 1.4.0. Note that this debug adapter is Windows-only. Cross-platform C++ debugging in the C/C++ Extension is done with the cppdbg debug adapter and this does NOT involve Concord.

Making an extension work

Making a Concord extension work in this scenario is very similar to the work for cross-platform .NET scenarios so this page will mostly defer to that documentation, and list differences:

1. No need to compile for .NET Core / Linux - the Linux part is probably obvious. This is subject to change in the future, but for now at least, any managed code in the vsdbg.exe process will run on the desktop .NET Framework.
2. No .pkgdef files: Like the .NET Scenario, if you have a .pkgdef file to register a language with the debugger then this needs to be converted to a .vsdbg-config.json file. One enhancement for native debugging is that a language has a codeViewCompilerIds property to specify mappings from code view language enumeration values.
3. .link files: Link files need to be dropped to %USERPROFILE%\.cppvsdbg\extensions
4. To debug your extension, the best option is to attach to the vsdbg.exe process