Obtaining the Concord API headers, libraries, etc

To build Concord extensions, the following things are needed -

1. Extensions implemented in managed code: reference assemblies
2. Extensions implemented in native code: API header files (VSDebugEng.h etc) and API import library (vsdebugeng.lib)
3. All extensions: vsdconfigtool.exe along with msbuild targets to run the tool. In Visual Studio 2019 (Dev16) and newer, this is Microsoft.VSSDK.Debugger.VSDConfigTool.targets, and previous releases used Microsoft.VSDebugger.targets and Microsoft.VSDebugger.Native.targets.

These can be obtained from the following packages from nuget.org:

Name	Description
Microsoft.VisualStudio.Debugger.Engine	Managed reference assembly for the Concord API.
Microsoft.VSSDK.Debugger.VSDebugEng	Native headers and import libraries for the Concord API.
Microsoft.VSSDK.Debugger.VSDConfigTool	Contains vsdconfigtool.exe -- the build tool for compiling .vsdconfigxml files along with msbuild target files for running it.
Microsoft.VisualStudio.Debugger.Metadata	Managed reference assembly needed for building 'Result Provider' managed expression evaluator components.

Note that before Visual Studio 2022, the headers, libs, reference assemblies and build tools could also be installed as part of the 'Visual Studio Extensibility' workload in the Visual Studio installer. For Visual Studio 2022 the reference assemblies were removed as part of a broader effort to shift to nuget packages. In the future, the remaining files may also be removed, so unless you have an existing extension that you don't want to migrate, it is recommended to consume all of these from nuget packages.