Debugger prints "You may only use the Microsoft .NET Core Debugger (vsdbg)..."
See original GitHub issuedotnet -info
:
/home/alex/Downloads$ dotnet --info
.NET Core SDK (reflecting any global.json):
Version: 2.2.402
Commit: c7f2f96116
Runtime Environment:
OS Name: ubuntu
OS Version: 18.04
OS Platform: Linux
RID: ubuntu.18.04-x64
Base Path: /usr/share/dotnet/sdk/2.2.402/
Host (useful for support):
Version: 2.2.7
Commit: b1e29ae826
.NET Core SDKs installed:
2.2.402 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.7 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
VS Code version:
Version: 1.43.2
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:52:11.516Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 4.15.0-91-generic
C# Extension version: 1.21.15
Steps to reproduce
Opened a folder with sln file and C# projects in it. Added the following launch configuration:
"configurations": [
{
"name": ".NET Core Launch (console)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
"program": "${workspaceFolder}/trigger_management/bin/Debug/trigger_management.exe",
"args": [],
"cwd": "${workspaceFolder}/trigger_management/bin/Debug",
"console": "internalConsole",
"stopAtEntry": false,
}
Clicked Run -> Start Debugging.
Expected behavior
The binary is executed
Actual behavior
Got the following message in debug console:
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
how to disable message "You may only use the Microsoft .NET ...
You may only use the Microsoft .NET Core Debugger (vsdbg) with Visual Studio Code, Visual Studio or Visual Studio for Mac software to...
Read more >[SOLVED] .NET Core, unable to debug in Visual Studio Code
You may only use the Microsoft .NET Core Debugger (vsdbg) with Visual Studio Code, Visual Studio or Visual Studio for Mac software to...
Read more >Debug a .NET console application using Visual Studio Code
This tutorial introduces the debugging tools available in Visual Studio Code for working with .NET apps.
Read more >Windows (10.0.19042) debugger (VS Code vsdbg and Visual ...
vsdbg is Microsoft .NET Core Debugger (vsdbg), no version information available, at $HOME\.vscode\extensions\ms-dotnettools.csharp-1.23.11 ...
Read more >Debug Your .NET Core Apps in WSL 2 with Visual Studio
And once your app is deployed, you can always use the Remote Debugger to attach to it if there is an issue. Getting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think I’m having the same issue, these are my logs;
Dotnet info
VS Code output;
VS Code version info
C# extension version: 1.21.17
@Perustaja if you installed VS Code from the Arch package repository: the problem is that you have the OSS version of VS Code, and the C# debugger is not licensed to work in non-Microsoft products. Please install VS Code from Microsoft if you would like to use the debugger from this extension.
If that is not your problem: please open a new issue. Unfortunately this issue is very generic, so, unless you look at a debugger log to see what failure is being reported, it is hard to guess if one person’s problem is the same as another. So I will lock it to prevent further comments.