SourceGear Support

Hi Adrian, I think you're on the right trail... there's probably a problem in the solution file with one or more projects and its probably related to SourceSafe specific bindings. Even though Microsoft fixed those issues with other types of solutions in the latest versions of Visual Studio, the prob...

Are you both using the latest version of SOS? Version 4.0.2? Are there any other developers on the project using VSS instead of SOS? I'd suggest backing up and then deleting your local copy of the project and then attempting an "open from source control" of the project from within Visual S...

Is the other developer working on the project using SourceSafe integrated into VS.NET instead of SOS?

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

Hi, Using SOS as my SCC, I'm opening a project in the .NET IDE. What's happening is, it asks me to check out all of the Project files (.proj) in my solution. Why? I'm not expecting to do any change in the project file itself. When, I'm working with sourcesafe as my SCC, it do not require me to do t...

As a test, if you use SourceSafe as your source control provider instead of SourceOffSite, then does Visual Studio give you the option of adding your cobol project to source control?

You're correct in that SOS doesn't support integration of a single solution with projects on different servers or databases. We'll have to add that as a feature request. I'm not even completely sure that the Microsoft integration APIs would support it.

Can you describe what happens when you try? What type of error do you see?

Let's first try doing a simple test first and see if that's successful for you and then go from there. Try this: 1. Start VS.NET with SOS as your source control provider and create a new C# Win app solution to be used as a test solution. Then do an "Add solution to source control". 2. Then...

Sorry, you're correct. I was only looking at it from the client's perspective. Here's what I should have told you to do instead. Its a bit more complicated, but it should work: Suppose you want to create keys for reaching an SOS Server using two different server names, A and B. 1. Create a key using...

It sounds like you must still have VSS specific info in your solution and project files. See the following article and the reply I posted to it. It sounds very similiar to your issue.

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

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 ho...

Import key files (*.iky) are named according to the user's name (for delivery purposes), but once the SOS Client has imported the *.iky, the *.key file is named according to the Server name. So you should be able to create two different keys in the Server Manager according to the different IP addres...

Earlier you asked about mapped drives. Since they are dependent upon the user logged into the machine, could you try using a UNC path instead? Configure your databases as UNC paths and then restart the SOS Server and see if that does make a difference.

Sorry, SOS doesn't currently support proxies that require authentication.