Why do some projects have MSSCCPRJ.SCC files and some not?

[JMLynch]

How do I make them go away?

If you have a project which has a MSSCCPRJ.SCC associated with it and you do a get on a new system or into a new working folder, when you open the project in VS2003 it shows binding errors and things are generally unhappy.

What I don't understand is why some projects have them and some don't.

This is a problem because if you fix the project bindings on a given system, when someone else gets that project the bindings are broken.

[lbauer]

The MSSCCPRJ.SCC file contains project bindings, which are associations between the project in the working folder to the project in the source code repository. The MSSCCPRJ.SCC file is created when you add a solution to source control, or open a solution from source control.
Users often make the mistake of doing a get with the Vault GUI client to bring the project to their working folder.

However the proper way to work with a project in source control is for one person to add the project to source control using Visual Studio 2003's File->Source control-> Add solution to source control.

Then each user who wants to retrieve that project would do an Open from source control with the command File->Source Control->Open from Source Control.

If the user already has a project on disk and wants to associate it with the version in source control, they can use the Change source control command to bind the solution and create the MSSCCPRJ.SCC file. They can also use this command is they are getting binding errors to unbind and rebind the project.

Note that older versions of Visual Studio wrote binding information in the project files so there may not have been a MSSCCPRJ.SCC file.
Vault's new VS 2005-style integration (VSIP) also writes the binding information into the project file, and does not use a MSSCCPRJ.SCC file.

More details here:

http://support.sourcegear.com/viewtopic.php?t=790

http://support.sourcegear.com/viewtopic.php?t=8535