Describe the feature you'd like
Who in the world thought that the new "C# PROJECT DETAILS" is a better idea than the previous "SOLUTION EXPLORER"???
The Solution Explorer allowed to have a CLEAN view of the project files without noise from the other filles/folders/temp files/temp folders!!!
Now the PROJECT DETAILS only shows Dependencies and we have to work with the File Explorer with all the noise that brings... Are you out of your minds???? (mantainers of C# Dev Kit)
This new update v1.120.0 or the C# Dev Kit update 3.20.195 (I don't know which of the two, I suppose Dev Kit) now creates a .lscache file for each .csproj so another more noisy file that we have to see in the File Explorer which would not have been visible in the Solution Explorer.
What's up with you? I sincerely don't understand this change.
Alternatives considered
With this change, anything but keep using VS Code
Environment Information
Debian Trixie
Describe the feature you'd like
Who in the world thought that the new "C# PROJECT DETAILS" is a better idea than the previous "SOLUTION EXPLORER"???
The Solution Explorer allowed to have a CLEAN view of the project files without noise from the other filles/folders/temp files/temp folders!!!
Now the PROJECT DETAILS only shows Dependencies and we have to work with the File Explorer with all the noise that brings... Are you out of your minds???? (mantainers of C# Dev Kit)
This new update v1.120.0 or the C# Dev Kit update 3.20.195 (I don't know which of the two, I suppose Dev Kit) now creates a .lscache file for each .csproj so another more noisy file that we have to see in the File Explorer which would not have been visible in the Solution Explorer.
What's up with you? I sincerely don't understand this change.
Alternatives considered
With this change, anything but keep using VS Code
Environment Information
Debian Trixie