Why will VS2005 check the project for editing without any changes?

Question

I have a VS2005 solution that contains many projects (C ++ DLLs, C ++ static libraries, C # assemblies, Windows C ++ executables) that combine several executables in various ways. For some reason, every time I open a solution, VS2005 wants to check out one of the projects for editing. The project has not been modified in any way; it is simply verified. If I configure VS2005 to request before verification, I can cancel the automatic verification at boot time without any bad effect that I can see. This may or may not be relevant, but the project that he continues to check is cppunit version 1.12.0 (static version of lib). How can I stop this annoying behavior?

Other potentially relevant (or not) details:

• Source control is Team Foundation Server (not Visual SourceSafe).
• no .suo or .ncb files are marked in
• .vcproj and .vspscc files are checked
• When I close the solution or close Visual Studio, they ask me if I want to save the changes to the project. The answer “yes” does not change the file (Kdiff3 compares my local file with the server version and reports that “the files have a binary equivalent”)
• Attempting to check for "modified" files results in a Visual Studio message "No change to register." All changes were either unmodified files or locks. Changes were rolled back by the server "

Answer 1

There are two reasons I came across that cause this behavior.

- . , , . :

• SccProjectName = "$////MyProject"
• SccAuxPath = "http://teamFoundationServer.example.com:8080"
• SccLocalPath = ""
• SccProvider = "{88888888-4444-4444-4444-BBBBBBBBBBBB}"

:

• SccProjectName = ""
• SccAuxPath = ""
• SccLocalPath = "SAK"
• SccProvider = ""

-. .vcproj, # XML, VB - , . "SAK", Visual Studio . . Alin Constantin.

, , , CppUnit 1.12.0! .

Answer 2

, Visual Studio .. , .

, , , . *.suo. bin obj , , ( ). ( . , ).

. VS2005, 2008.

?

,

Answer 3

, .suo .ncb ?

Answer 4

VS2005 , cppunit, , - ?

- Web App, , .

Answer 5

, , , Visual SourceSafe2005 , Visual Studio. (FYI, Visual SourceSafe VSS.)

VSS. , Visual SourceSafe: , , - , , .

- , Subversion . , Visual SourceSafe . Visual Studio VisualSVN, IDE (, ..), VSS.

, , Visual SourceSafe " " - , , Subversion . , , , , , , , .

Answer 6

, , , . VS , , ,

, , , , " ...", , .

.sln GlobalScxtion (SourceCodeControl) , , , , - , " ...", , , .

Answer 7

cppunit, , , . .

, ? , ?

Answer 8

Very often, this behavior is caused by VS trying to update version control bindings.

Graham is right, VS will not save project or solution files until you close VS.

I would let VS check the files, then close the VS, and then split them.