dotnet / dotnet/project-system

Dependencies tree should appear immediately

Open
#9,710 0 comments 0 reactions 0 assignees View on GitHub
Feature-Dependency-Node Performance-Scenario-Solution-Explorer Performance-Scenario-Solution-Open Tenet-Performance Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

(As discussed in: https://github.com/dotnet/roslyn/pull/78778#discussion_r2122383650)

The dependencies tree builds itself using data from both evaluation and design-time builds. The expectation is that it appears immediately after the first evaluation of a project, meaning it should appear populated along with the rest of the tree.

However, while testing another issue, intentionally [delaying design-time builds](https://github.com/dotnet/project-system/blob/main/docs/repo/debugging/design-time-builds.md#delaying-design-time-builds) caused the tree to appear with the same delay, suggesting that the tree is not appearing as early as it should.

Fixing this would improve perceived performance but reducing the number of tree updates. It might also any expansion state in the tree to be restored when a solution is reopened. It'll also reduce the number of tree updates, which are relatively expensive operations in CPS.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.