VS.NET 2003 SccProvider changes

[Jason]

Hi -- I'm currently using SOS Pro 3.5.1 with VS.NET 2003 and have a bit of a problem.

We have two engineering teams at different sites working on the same project. Naturally our source control servers (VSS 6) are hosted at one site; all the developers at said site simply use the standard VSS client. Our developers at the remote site use SOS 3.5.1 on the exact same underlying VSS project.

As it turns out, VS .NET changes .csproj project files to reflect the default souce control providers on load. This presents a bit of a problem: since all the project files are in source control with VSS as the default provider, just loading the solution forces the remote team's copies of VS .NET to check out every csproj file. The only difference that is made is that SccProvider = SourceOffSite instead of SccProvider = Microsoft Visual SourceSafe. Consequently, the remote team must undo these checkouts and get the latest versions of the project files actively each day since they don't get automatically updated on get latest.

This is not a critical bug, but it does add up to a substantial amount of frustration and lost time. Has anyone else encountered this problem? Is there a known solution??

TIA,
Jason

[lbauer]

This is a known issue in earlier versions of SOS. I'd suggest you upgrade to SOS 3.5.3, which is still available from the SOS Downloads section at:

http://www.sourcegear.com/sos/downloads.html

We fixed some binding problems when SOS and VSS users both use the same projects.

Also see this article about SOS 4.0 and VSS:

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