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.
You should not check .vs into source control.
It just contains temporary caches used by Roslyn.
You should not check .vs into source control.
It just contains temporary caches used by Roslyn.
Yes, I agreed with SLaks - you can add .vs folder to ignore list - in fact you should do this on the beginning.
.vs contains more then only 'Roslyn cache' - but all stuff stored in this folder is 'working' or 'temporary'... It's means that is not required for storing solution/project - you can delete it when VS is shutdown and after that VS will recreated it when launching the solution - of course you lose your working configuration of the IDE, but no worries, it's not painful.
When you working with ASP.NET - you can find configuration of IISExpress inside .vs folder - and sometimes deleting this file can be very useful - like I said it will be recreated with 'fresh' settings when you lunch VS next time...
You can use .tfignore file rules for excluding some folders and files. It's practice very similar to .gitignore when you use Git, but for Team Foundation Version Control. Just create your file with your custom rules and start to use it.