I fixed it by replacing all the values ββ"<>" in the style of launch.json
as follows (the project in my case is called "sample01"):
{ "version": "0.2.0", "configurations": [ { "name": ".NET Core Launch (console)", "type": "coreclr", "request": "launch", "preLaunchTask": "build", "program": "${workspaceRoot}/bin/Debug/netcoreapp1.0/sample01.dll", "args": [], "cwd": "${workspaceRoot}", "stopAtEntry": false, "externalConsole": false } } }
As you can see, I use only one configuration, which is called ".NET Core Launch (console)". This name can be changed, and you will see it when you click on the debug menu in the far left corner (that is, with an error symbol) and look at the very top.
Now I have entered the full path of my build-config (which is .NET Core 1.0 in my example) and it works.
So, yes, you will have to do this manually if it is preconfigured with "<>" elements. If you are using dotnet new
, then code .
to output new projects, new versions of Visual Studio code will now create launch.json
ready for launch.
source share