In VSCode (not Insiders) I am seeing this error in a dialog box when hitting F5 to compile in Ubuntu:
The preLaunchTask 'build' terminated with exit code -2.
In the terminal window itself, this error is reported:
The terminal shell path "dotnet" is a directory
Version: 1.37.1
Commit: f06011a
Date: 2019-08-15T16:17:25.463Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-58-generic
This error is new, happens on all projects on this machine, and the errors began after installing updates.
BUT PLEASE NOTE: I have been aware that my dotnet folder is itself named dotnet -- not the (standard, I believe?) name .dotnet with a leading period. This is unorthodox, and due to the error message I was seeing, I decided now was a good time to align my machine with the norm. I renamed my folder to .dotnet and adjusted as necessary stuff in my .bashrc file.
Rebooted, and error is gone.
That said, I do think this is a bug in the latest version of VSCode. In older versions I did not have this problem.
In VSCode (not Insiders) I am seeing this error in a dialog box when hitting F5 to compile in Ubuntu:
The preLaunchTask 'build' terminated with exit code -2.
In the terminal window itself, this error is reported:
The terminal shell path "dotnet" is a directory
Version: 1.37.1
Commit: f06011a
Date: 2019-08-15T16:17:25.463Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-58-generic
This error is new, happens on all projects on this machine, and the errors began after installing updates.
BUT PLEASE NOTE: I have been aware that my dotnet folder is itself named dotnet -- not the (standard, I believe?) name .dotnet with a leading period. This is unorthodox, and due to the error message I was seeing, I decided now was a good time to align my machine with the norm. I renamed my folder to .dotnet and adjusted as necessary stuff in my .bashrc file.
Rebooted, and error is gone.
That said, I do think this is a bug in the latest version of VSCode. In older versions I did not have this problem.