Add Docker Files to Workspace generates invalid tasks.json referencing a non-existent .sln file when C# Dev Kit is installed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, typescript, vscode
- Domain
- build-system, devtools
Research direction
Reproduce the Add Docker Files to Workspace flow with the dotnet new mvc project, then inspect the generated .vscode/tasks.json and the project’s .csproj file. Compare the task reference with the files actually created, and run dotnet build to confirm the project builds; done means the generated tasks.json references the existing project file and the image build no longer fails.
Written by the indexing model from the issue text.
Description
OS: Win 10
Build Version: 20260902.2
Repro Steps:
- Install C# Dev Kit
- Create a new project: dotnet new mvc -n DotnetApp0903
- Open the project folder in VS Code->Add Docker Files to Workspace
- Inspect the generated .vscode/tasks.json.
Expect:
Generated tasks.json should reference the existing project file(DotnetApp0903.csproj) instead of a non-existent solution file.
Actual:
Generates invalid tasks.json referencing a non-existent .sln file and lead to build image failed.
More Info:
- This issue doesn't repro when separately install C# extension
- The project was created using: dotnet new mvc
- The generated project contains DotnetApp0903.csproj and no .sln file.
- Running "dotnet build" succeeds.
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 93
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-containers
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-containers#655 ·
Maintainers usually reply within 1 day
-
Compose Down fails for projects started with multiple --env-file argumentsPossibly taken @sylvesterkaczmarek claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/vscode-containers#653 ·
Maintainers usually reply within 1 day
-
Add localization (i18n) support, starting with Simplified Chinese (zh-cn)Possibly taken @linghengqian claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-containers#648 · 3 comments ·
Maintainers usually reply within 1 day
-
.NET AT-CTI blocked external
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-containers#623 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
engineering
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/vscode-containers#594 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/vscode-containers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
backnotprop/plannotator#2914 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dsh-tauri-desk/deepseek-harness-desktop#1477 · 1 comment ·
-
[docs] RELEASE.md: wrong branch name, no check that the prepare PR merged with the right subject, manual publish stepPossibly taken @albertteoh claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jaegertracing/jaeger-ui#4739 ·
Maintainers usually reply within 1 day