Closed gregg-miskelly closed 4 years ago
For this step:
Create a VSCode Codespaces instance with default .NET Core console app template in Windows Codespaces (doesn't repro with Linux)
How do I get the default .NET Core console app template?
@alexr00 If dotnet is installed, you can run dotnet new console
from the terminal. docs
Looks like findExecutable
needs to be moved to the extension host. This wasn't needed before because it's only required for Windows, and we didn't have Windows remotes.
Encountering the same issue with dotnet new webapp
.
I can get around this with using the absolute path in command:
"tasks": [
{
"label": "build",
"command": "C:\\Program Files\\dotnet\\dotnet.exe",
"type": "process",
"args": [
"build",
"${workspaceFolder}/QBCart.Server.Client.csproj",
"/property:GenerateFullPaths=true",
"/consoleloggerparameters:NoSummary"
],
"problemMatcher": "$msCompile"
},
...
]
I tested with an SSH Windows remote, and I see the executable path being correctly found now. Please let me know if you try it out in the next insiders build!
I'm using a windows codespace, with the build from 7/23, and I think I still see this issue
Interesting. I tried it with a windows codespace and got:
C:\Program Files\dotnet\dotnet.exe build C:\workspace/TestCodespacesWindowsAndVSCode/TestCodespacesWindowsAndVSCode/TestCodespacesWindowsAndVSCode.csproj /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary <
This is with the build from 8/3. Not sure what could be going on here. I'm going to close and see if someone else can verify.
This issue is from a bug opened by @kendrahavens (https://github.com/OmniSharp/omnisharp-vscode/issues/3878)
Steps to Reproduce:
build
task.Result:
tasks.json tries to run dotnet.exe from
C:\workspace\dotnet
instead of from where it is installed, and so it fails.Terminal output
tasks.json