Should I add the Visual Studio 2015 .vs folder to source control?

git svn version-control visual-studio-2015 ignore
SoftwareFactor picture SoftwareFactor · Aug 7, 2015 · Viewed 97.1k times · Source

Visual Studio 2015 creates a new folder called ".vs". What is the purpose of it and should I add it to source control?

Answer

Patrick Quirk picture Patrick Quirk · Aug 7, 2015

No, you should not add it to source control. The purpose of this folder is to move machine- and user-specific files to a central location. The explanation on the Visual Studio User Voice issue explains it well:

So far, we have moved the .SUO file and the VB/C# compiler IntelliSense database files to the new location. All new project specific, machine local files will be added to the new location too. We plan on taking this even further in future releases and are investigating how to improve the directory structure of build output and other existing files that can clutter the source tree.

These are all files that you would never check in, since they are generated from a build or contain machine-specific information.

Related questions

How do I migrate an SVN repository with history to a new Git repository?

I read the Git manual, FAQ, Git - SVN crash course, etc. and they all explain this and that, but nowhere can you find a simple instruction like: SVN repository in: svn://myserver/path/to/svn/repos Git repository in: …

Read More
Should I use SVN or Git?

I am starting a new distributed project. Should I use SVN or Git, and why?

Read More
How and/or why is merging in Git better than in SVN?

I've heard in a few places that one of the main reasons why distributed version control systems shine, is much better merging than in traditional tools like SVN. Is this actually due to inherent differences in how the two systems …

Read More