microsoft / microsoft/vscode-containers
Add Docker Files to Workspace generates invalid tasks.json referencing a non-existent .sln file when C# Dev Kit is installed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
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.
Contributor 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.
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.
Assessment
- Tech stack
- docker, typescript, vscode
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100