Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtering custom runtimes with cppvsdbg in VSCode #116

Open
int19h opened this issue Jun 13, 2024 · 0 comments
Open

Filtering custom runtimes with cppvsdbg in VSCode #116

int19h opened this issue Jun 13, 2024 · 0 comments

Comments

@int19h
Copy link

int19h commented Jun 13, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant