.scc files missing?

[Katatonia]

We are using Visual Source Safe 6.0 on some computers and SourceOffSite 3.5.3 on others. And now there's a problem: when we create project and add it to source control using Visual Source Safe. When that project is retrieved to another computer, using SourceOffSite, no .scc files (including mssccprj.scc) are created. As a result, the project is not under source control. We are using Microsoft Visual Studio .NET.
How should we deal with this problem?

[Katatonia]

Same problem occurs when project is added to Source Safe using SourceOffSite - when another user retrieves project, .scc files are missing and the only workaround for that user is to overwrite project by performing "Add Project to Source Control".

[corey]

How are you retrieving the projects on the other computers? Are you using the SOS Windows GUI Client, or are you performing an "open project from source control" from within VS.NET?

The SOS Windows GUI Client does not create SCC files, you must use SOS integrated within VS.NET for SOS to create those files.

On the other machines that need to retrieve the projects, setup SOS as your default source control provider, and then within VS.NET do the following: File -> Source Control -> Open From Source Control

[corey]

One more thing: if you're wanting to work on a solution where some developers use integrated VSS and some use integrated SOS on the same solution, this can be tricky. The problem is, some SCC provider information gets stored in the project files by VS.NET, causing conflicts between SOS and VSS.

This problem has been greatly reduced in the upcoming SOS 4.0 release, when the other developers using VSS are using VSS version 6.0d. VSS 6.0d and SOS 4.0 both make use of the latest SCC integration APIs, which reduces the amount of SCC information that VS.NET places in project files.