Menu
What's the best practice for excluding/including the .vs folder for a VS 2015 solution in source control?
After an initial build/edit I only see a .suo file created so far at '[Root]/.vs/[SolutionName]/v14/.suo', so I'm assuming that's the replacement for the old '[SolutionName].suo' and should be excluded (generally) - but will other settings/etc be placed there in some scenarios that I might want to version?
From this uservoice, I'm guessing the answer is that it should be ignored, just wanted a confirm before I updated all my machine settings since I didn't see it in any local docs.
287
There's a . vs folder created right next to . sln solution file. Under Project->Properties->Configuration Properties->General there is already an entry for Intermediate Directory.
Yes, you can delete it. visual studio will simply recreate that folder for you.
When you delete the vs folder, you may lose user state related to solutions such as build configurations, local debug settings, open tabs, Project Configuration such as Profile type, Launch type , and so on. But deleting the . vs folder will not create any impact on: Solutions and projects.
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 .
You should not check .vs into source control.
It just contains temporary caches used by Roslyn.
134
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
