11

Visual Studio 2017 (I've also seen this referred to as Visual Studio 15 2017, confusingly enough) introduces "Open Folder" support with CMake integration. In this case, it creates a few new files in my working copy. Here is what I noticed:

.vs/ProjectSettings.json
.vs/slnx.sqlite
.vs/source/v15/Browse.VC.db
CMakeSettings.json

It seems obvious that CMakeSettings.json goes into version control. But what about the contents of the .vs/ directory? If it helps to provide examples, I'm using Git for version control, so I'd need a reliable set of patterns to put into my .gitignore file.

EDIT:

People are marking my question as a duplicate, however that is incorrect. This is not a duplicate because VS 2017 adds several new files to my working copy that were not used in previous versions of Visual Studio. As such, it's important to my question from the proposed duplicate questions.

void.pointer
  • 23,191
  • 28
  • 120
  • 213
  • 1
    https://www.gitignore.io/ – Philippe Nov 22 '16 at 19:30
  • *referred to as Visual Studio 15 2017* where did you see that? I've seen *15* and *2017* (just like you had 14 and 2015), but both? – stijn Nov 22 '16 at 19:48
  • https://www.gitignore.io/api/visualstudio seems to have a ton of stuff, but I did not find references to `slnx` so not sure if it covers the version of VS that you are using. – Ashutosh Jindal Nov 22 '16 at 21:18
  • Possible duplicate of [.gitignore for Visual Studio Projects and Solutions](http://stackoverflow.com/questions/2143956/gitignore-for-visual-studio-projects-and-solutions) – Jimmy Nov 27 '16 at 18:56

2 Answers2

12

https://www.gitignore.io/api/visualstudio is considerably the definitive starting point for a project in Visual Studio. Do read through it, as there are a couple sections to uncomment depending on how your project may be structured.

If you create a new project in VS2017 and add it to source control, or add an existing project to source control, VS will actually add a copy of this file to your repo as well. It seems though that the Open Folder functionality doesn't quite have that level of git integration exposed yet (there was no Add to Source Control that I could find).

Jimmy
  • 25,492
  • 5
  • 84
  • 93
3

Files in .vs/ directory don’t need to control versions. It’s just like VS 2015, .vs folder contains some config setting files and machine local files etc. You can refer VS uservoivce.

Martin Backasch
  • 1,741
  • 3
  • 22
  • 28
Marina Liu
  • 35,020
  • 4
  • 56
  • 68