In the previous non-dotNet era, VSS only generates a vssver. scc file. to cancel the VSS function, you only need to delete the file and change the file attribute to non-read-only.
Recently, the VSS feature was used in dotNet, but there was a problem with undo. Deleting the added files separately cannot remove the VSS feature, after the study, we found that VSS in dotNet is very different from previous versions. It not only adds several files, but also modifies the information of some files, you need to use the following methods to delete the source code management environment:
1: Delete mssccprj. scc and solution name. Vssscc, vssver. scc, and project name. Csproj. vspscc File
2: In the project name. Vbproj contains information similar to the following:
SccProjectName = "SAK"
SccLocalPath = "SAK"
SccAuxPath = "SAK"
SccProvider = "SAK"
3: finally. Find and delete the VSS information in the sln file.
GlobalSection (SourceCodeControl) = preSolution
SccNumberOfProjects = 4
SccLocalPath0 =.
CanCheckoutShared = false
SolutionUniqueID = {77652F52-DA0D-4E0B-AC65-ACBAD5F49A1B}
SccProjectUniqueName1 = dibdb \ dibdb. vbproj
SccLocalPath1 =.
CanCheckoutShared = false
SccProjectFilePathRelativizedFromConnection1 = dibdb \
SccProjectUniqueName2 = eeinfo \ eeinfoclient. vbproj
SccLocalPath2 =.
CanCheckoutShared = false
SccProjectFilePathRelativizedFromConnection2 = eeinfo \
SccProjectUniqueName3 = http: // mingday/temp/eeeinfo. vbproj
SccProjectName3 = u0022 $/abcd/WebServiceu0022, u0020DAAAAAAA
SccLocalPath3 = WS \ eeinfo
CanCheckoutShared = false
SccProjectEnlistmentChoice3 = 2
EndGlobalSection
Now, the source code management function of the environment is no longer available.