title: What issues can arise from checking in .vssscc and .vspscc files into source control?
body: <p>There seems to be some consternation about two file types that, in my case, TFS checks in when a new solution or project are created: .vssscc and .vspscc files.</p>
  
  <p><a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/9920911d-1a7e-4ada-90cd-b1b910586cf4/why-do-you-need-the-vspscc-and-vssscc-files?forum=tfsgeneral">I found a page</a> that describes that these files are for, and <a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/d54e7126-eb15-4616-a2b6-afc71dc25fcf/should-we-normally-check-source-control-files-vssscc-vspscc-in-?forum=tfsversioncontrol">yet another</a> that recommends checking them in. I'm perfectly fine with this, but I have heard some grumblings in the internet that these files can cause issues with collaboration between projects, such as merge conflicts and project load errors.</p>
  
  <p>I do recall having some issues in my own organization where the .vspscc file caused some issues, where a developer had caused some edits to it and didn't check it in with the rest of his changes. We were able to repair easily, however.</p>
  
  <p>My question is: what issues should I be aware of, and in the case that issues exist, what precautions can I recommend to my organization to avoid any trouble?</p>