If I understand everything correctly, an extension providing a custom runtime that is registered in accordance with https://github.com/microsoft/ConcordExtensibilitySamples/wiki/Support-for-VS-Code-cppvsdbg-Scenarios would be automatically loaded, and that runtime would participate in the Concord debug session. However, it may be desirable to allow users to enable or disable a custom runtime for any given debug target in launch.json (similarly to how in VS, one can pick "code type" in the Attach to Process dialog, so that one can e.g. do pure native debugging of a process that has managed code in it). Is there some standardized approach for handling that in VSCode?
If I understand everything correctly, an extension providing a custom runtime that is registered in accordance with https://github.com/microsoft/ConcordExtensibilitySamples/wiki/Support-for-VS-Code-cppvsdbg-Scenarios would be automatically loaded, and that runtime would participate in the Concord debug session. However, it may be desirable to allow users to enable or disable a custom runtime for any given debug target in launch.json (similarly to how in VS, one can pick "code type" in the Attach to Process dialog, so that one can e.g. do pure native debugging of a process that has managed code in it). Is there some standardized approach for handling that in VSCode?