SourceGear Support

Thanks Beth, but I think I got it. (I will keep that debug mode in mind :). I was using the WAN IP and port number to connect instead of the computer's LAN IP and port. The WAN is supposed to work when we connect from off-site but for some reason it is not. But I typically connect from inside the ne...

That is what I am doing to get the error described above. It lets me log into source control and navigate to the folder where the solution is, and it asks to create a new folder, but then the closed connection problem.

I am using SOS Client 4.2 and VS2005 and VS2008. I can connect, log in, and navigate a SourceSafe repository just fine using the SOS client. But when I try to get from source control using VS2005, VS hangs/crashes. With VS2008, I keep receiving this error: "SourceOffSite: The connection to the ...

I normally use SOS 4.x, but had to reinstall so I downloaded the newest (5.0.3). When trying to connect to the server, I get an error:

"The server you are connecting to has an invalid protocol version for this client."

What does this mean and can I do anything about it?

We use SourceOffSite for the VSS client. A single database for everything makes lots of sense to me, but I don't know if others would go along with it. What is the scenario you are thinking of? We don't use comments, but I don't see how that would help find code. We "use" Bugzilla for bug ...

Yes, we do have to fix bugs from previous releases. To do this, our new plan is to fix the bug in the development code, and then manually duplicate the changes in the previous release production code. The reason we fix it in development first is that in the past, we would fix a bug on the release ve...

What I mean is that we have multiple VSS databases. They are all the same code, just at different points in time. They are like "snapshots" so we can go back and fix bugs and redeploy without deploying all of our new unfinished code. I think that is where labels should come in, but suppose...

Actually we just had a meeting about all of this. I really wish I could have recorded it. Our system is a nightmare. Anyway, we actually have many repositories. PRODUCT1_DEVELOPMENT $/ |----Bugzilla |----Docs |----Learning |----|----random stuff |----Network |----PRODUCT1 |----|----some random stuff...

I would really appreciate some help setting up an efficient method of using our source control system. We are using SourceSafe and SourceOffSite. We spend half of our time managing our source code, and have even lost customers over it in the past. We have 3 main customers for our primary project, an...

I'm sorry for taking so long to reply. I would love to know if these lengthy get times (due to client CPU load) are normal for a get from within visual studio (vs relatively quick gets from within SOS client). And I would love to know for sure the cause of the problem. And I would love to be able to...

When I open in VS the solution for which I did a Get in SOS client, it says: The solution appears to be under source control, but its binding information cannot be found. It is possible that the MSSCCPRJ.SCC file or another item that holds the source control settings for the solution, has been delet...

A Get on my client machine with SOS client does not use much CPU power compared to a Get in VS. It takes 7 minutes compared to roughly an hour. However, the way things are configured, it is not getting exactly the same files; I think it is actually getting more data with SOS client. So I don't know ...

Well, the SOS server machine doesn't have visual studio on it. But I could do a get directly from my development machine's SOS explorer, just to see if it has the same problem as a "get from source control" from VS. In that case a recursive get from the SOS server machine would be an effec...

Thanks Beth. I am gone for the weekend. I appreciate your help. Let me know if you need any information from me.

Please let me know if you have ideas. Thanks very much.