dotnet / dotnet/project-system

Please fix the .vspscc problem

Open
#1,801 33 comments 55 reactions 0 assignees View on GitHub
Feature-Project-File-Simplification Triage-Approved
Dominant language
C#
Stars
1k
Forks
415
PR merge metrics
No merged PRs in 30d

Description

`{ProjectName}.vspscc` files continually get recreated in each project folder and are now shown in Solution Explorer. It has been irritating enough that they have to exist in the first place, and continually get added to pending changes even though the contents never change and are all in fact identical with each other. Now we have to look at them in Solution Explorer or add boilerplate to every new csproj we create, which is almost as bad because we shouldn't have to dirty everything. The vspscc files should not exist in the first place.

https://social.msdn.microsoft.com/Forums/vstudio/en-US/9920911d-1a7e-4ada-90cd-b1b910586cf4/why-do-you-need-the-vspscc-and-vssscc-files
This was acknowledged by Microsoft in 2005; in 2010 "We are looking into improving this in the future version of Visual Studio"; now, especially with the new csproj format, please do the right thing and cut these files.

All ignored files are handled via `.tfignore`. These files are purely vestigial and are irritating on a daily basis.

Every single .vspscc has precisely these contents which never change, even though the files show up in Pending Changes all the time:

```
""
{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "NEVER"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "0"
"ORIGINAL_PROJECT_FILE_PATH" = ""
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}
```

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.