microsoft / microsoft/vscode-dotnettools

[v11] C# Project Details does not show a solution node

Open
#3,530 0 comments 0 reactions 1 assignee View on GitHub

@drewnoakes is already working on this.

Since Sep 17, 2026.

bug v11
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the issue

In C# Dev Kit v11, the C# Project Details view shows projects directly at the root and does not include a solution node. This occurs both when a solution is open and when C# Dev Kit is running in workspace development mode.

Without a solution node, the tree does not represent the solution-to-project hierarchy and makes it harder to understand which solution contains the displayed projects.

Collect logs

Not collected.

Steps to reproduce
With a solution open
  1. Open a C# solution in VS Code.
  2. Open the C# Project Details view.
  3. Observe that the project appears at the root of the tree and no solution node is shown.
In workspace development mode
  1. Open a C# workspace in workspace development mode.
  2. Open the C# Project Details view.
  3. Observe that projects appear at the root of the tree and no solution node is shown.
Expected behavior

The C# Project Details view should show a solution node with its projects nested beneath it, both when a solution is explicitly open and when using workspace development mode.

Actual behavior

Projects are displayed directly at the root of C# Project Details. The status bar identifies the active solution, but the corresponding solution node is absent from the tree.

C# Project Details shows a project without its solution node

Environment information
  • C# Dev Kit version: v11
  • Reproduces with: An open solution and workspace development mode

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.