Deemphasise an initial configuration provider if an extension is installed.

[WardenGnaw]

I'm looking to either remove or deemphasise a debugger selection from the dropdown for initial configuration providers if an extension is installed.

For example, I'm looking to hide the .NET 5 and .NET Core debugger if C# Dev Kit is installed.

The other ideal is that we could somehow show a Dynamic Configuration Provider C# even though no file context is present.
E.g.

[roblourens]

So your extension provides those configurations? So you are in control of whether they show up, right? So what do you need?

[WardenGnaw]

I have two asks here:

1. What is a good way to hide .NET 5+ and .NET Core from the debugger dropdown list without unregistering the debugger since we still want to provide that functionalty if they do not have the C# Dev Kit extension installed.

2. Is it possible to show the C# Dynamic Configuration provider if no file is selected. Instead of acting on a specific language/file, it just works on the opened folder.

[roblourens]

Sorry I still don't understand what you're asking me for, do you control the extension or are you trying to suppress another extension's functionality?

[WardenGnaw]

I control the extension. My extension will check if another extension is installed and would like to remove itself from the debugger list that is presented to users, but still be able to have its resolveDebugConfigurations API be called.

[roblourens]

I'm on board now, I missed the detail that this involves the static initialConfigurations. Does the C# Dev Kit totally take over the debugger functionality? What happens if I have a c# launch config already configured?

If you want to disable your debug adapter entirely, there is an option to include a when clause on your debugger contribution, and you could set that to a context key that you control, I think that would do it.

If you are trying to keep the debugger enabled in this case but just remove it from that one menu, then I might need to hear more details about the relationship between the two extensions, and we can set up a call if that's easier.

[WardenGnaw]

Does the C# Dev Kit totally take over the debugger functionality? What happens if I have a c# launch config already configured?

We want to emphase on the C# Dev Kit experience with the dynamic configurations over using initial configurations since to simplify the experience of using Visual Studio on Windows to VS Code (for any platform) we are utilizing launchSettings.json.

So I am looking for "If you are trying to keep the debugger enabled in this case but just remove it from that one menu,"

I might need to hear more details about the relationship between the two extensions, and we can set up a call if that's easier.

Sounds good. I'll find a time on your calendar.

[roblourens]

We discussed allowing the C# extension to disable just the initial configurations for its base debug adapter type via a when clause. That will lead the user down the right path when they want to set up debugging and have the dev kit extension installed.

[vscodenpa]

Friendly ping! Looks like this issue requires some further steps to be verified. Please provide us with the steps necessary to verify this issue.

[roblourens]

Have you implemented this in C# @WardenGnaw?

If not, verification steps for us

• Add or modify a debugger contribution to include a hiddenWhen context key
• When that key is true, the debugger should be hidden from the debuggers list that you get eg when you don't have a launch.json and you click the button to create one or start debugging

[WardenGnaw]

Yep! This was added in dotnet/vscode-csharp#6405

[roblourens]

Alright, assuming that it's working for you as expected, I'll mark this as verified