SourceOffsite requests to check out all project files

[Sungard-Enform]

We have two groups working on a particular project: One group is local and uses SourceSafe while the remote group is trying to use SourceOffSite. I have read the post 'SourceSafe and SourceOffSite are Fighting' as well as 'Binding a solution to both SOS and VSS'. Only the registry hack from 'SourceSafe and SourceOffSite are Fighting' works in our situation. Without hacking the registry, SourceOffSite wants to check out all of the related project files and change the following line:
SccProvider = "MSSCCI:Microsoft Visual SourceSafe"
To SccProvider = "MSSCCI:Source OffSite". Since the client machines need to use both SourceOffSite and SourceSafe, the registry hack will not be an option. The version of SourceSafe is 6d and the version of SourceOffSite is: 4.0.2. What are my options?

Thanks,

[corey]

If you still have lines like SccProvider = "MSSCCI:Microsoft Visual SourceSafe in your project files, then that's the problem. In order to have a split team on SOS and VSS working on the same project, you cannot have vendor specific info in those files.

The following article tries to explain how to "fix" projects like your's so that you can support both SOS and VSS at the same time:

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

The unbinding process that's mentioned in that article is supposed to remove all of the vendor specific info from the project files, but if it doesn't, then you'll need to remove that info manually before you rebind the project to either SOS 4.0.2 or VSS 6.0d. All vendor specific info MUST be located in the accompanying MSSCCPRJ.SCC files in order for your desired scenario to work correctly.

Also, as a proof of concept, create a new test solution (you can delete and remove it later) and add it to source control using integrated SOS 4.0.2. Then close the solution in VS.NET and open the .sln and .proj files in a text editor and you should see that there is no vendor specific info in those files.

[Arvin]

Do you also need to have 6.0c installed on the server? Or 6.0c installation on the client workstations will be fine?

[corey]

For this particular issue, just the client machines should be enough.