This one is for real beginners, though it just stroked me now, after too many years of developing: many times I wondered how come the following scenario doesn’t work:

1) On one machine you create a simple Visual Studio solution + project, bounded to Source Control (Source-Safe \ Vault \ whatever).

2) Then you go to another machine, open the Source Control client (Source-Safe itself) and get the latest version of the newly created solution.

3) Now you try to open the solution in Visual Studio, to no avail; for some reason it’s impossible to bind it. VS tells you “The associated source control plug-in is not installed or could not be initialized”, offering you to “Temporarily work uncontrolled”, etc… You can spend your entire day trying to bind and unbind and it just won’t work, cause if you recreate the binding info and check them into the source control, then the first machine won’t work. It’s frustrating.

Anyway, the problem lies in section (2) – instead of getting the latest version through the source control client, you should have opened Visual Studio and choose: File|Source Control|Open from Source Control… this would have created the solution on the second machine with no binding problems.

Actually, what missing in section (2) are the “MSSCCPRJ.SCC” files for the solution and project. These file are not kept in source control (by default), and in fact if you would apply section (2) and then copy the files, everything will work just fine.