Removal of source control information from .proj and .sln files
Applies to: 
Visual Studio 
Visual Studio for Mac
Note
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
In version 1.2 of the Source Control Plug-in API the SCC information is stored in a MSSCCPRJ.SCC file. The advantage of the MSSCCPRJ.SCC file is that the SCC information is not source-controlled, like it is in .proj and .sln files.
Version 1.2 Changes
In source control plug-ins that are based on the Source Control Plug-in API version 1.1, information about source control is stored in the project (.proj) and solution (.sln) files. The database location of the source control information is specified by the AuxPath, and the specific location within the database is specified by ProjName. This behavior can cause problems after branch, fork, or copy operations because the ProjName would typically be invalid after any of these operations.
In the Source Control Plug-in API version 1.1, the IDE used ~SAK files to detect if a plug-in supported the MSSCCPRJ.SCC method of storing source control information. The Source Control Plug-in API version 1.2 provides a new capability for detecting the support for MSSCCPRJ.SCC file without using a ~SAK file. For more information, see Elimination of ~SAK Files.