-
Notifications
You must be signed in to change notification settings - Fork 34.8k
Closed
Closed
Copy link
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded
Milestone
Description
- VS Code Version: 1.80.1
- OS Version: Windows_NT x64 10.0.19045
Steps to Reproduce:
- Install C# dev kit
- Clone C# extension and start debugging the extension
- Create a .NET console app (I tried .NET 6 or .NET 7)
- Open
Program.cs
and click F5. Select C#:
Expected
The debugger gets queried for its configuration variables and start debugging.
Actual
C# extension registers two debug providers, but the second provider, BaseVsDbgConfigurationProvider.resolveDebugConfigurationWithSubstitutedVariables
(which implements vscode.DebugConfigurationProvider
) is never called.
Remarks
- If you have a launch.json with a profile type specified (only one provider is used), step 5 is called.
- If you start debugging from the project in Solution Explorer window (from C# dev kit extension, so only one provider is used), step 5 is called.
This is the launch request for the repro scenario:
-> (C) {"command":"launch","arguments":{"name":"C#: ConsoleApp47","request":"launch","type":"coreclr","launchConfigurationId":"TargetFramework=;ConsoleApp47"}
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded