SourceGear Support

Thanks! I'll look forward to v5.0 then!

Just a slight update, This has become an even bigger issue for me now, since our application is setup as several applications, I need more than one copy of DevStudio open to debug these most of the time. Quite often during debugging DevStudio decides to update source control status, and inevitably i...

Yes, please do. Thank you.

I have seen this several times before, and on different versions of the client. Currently, I am on 4.2, and using Visual Studio 2005. I find sometimes Visual Studio is connected properly to SourceSafe via. SOS, and when I go to use the client (for labeling features), the client will never connect, a...

Currently, my projects are all working because I have re-connected them (not using the VS bind ability). All of them are .vcproj files.

Would it be helpfull if the next time it happens, I contact you, and we can try some things, or I can send you project/database files?

No, sorry, I have not. Our database is too large, and VSS is quite slow in our remote location.

Our other office (whom uses VSS), has never seen this problem, so I assumed it was a SOS related issue.

This problem happens to me a lot of the time as well on a bind operation with SOS as a client.

Unfortunatly, it makes reconnecting to projects painful, since the only work around I have found is to open it from source control after removing the project from the solution.

I used to be able to get it to unlock by starting the client up, and closing it before opening VS, but now that's not working anymore. I just tried deleting the database file and rebuilding it, and it deleted ok, which tells me there is actually no locks on the file, yet VS 2005 still hangs trying t...

I could do that, but unfortunatly, since our tree is rather huge, and located in a different city, it takes 20 minutes to rebuild it... not something I really want to be doing that often.

Does anyone know if you can "reset" the lock on the file without rebooting/deleting the file?

I am experiencing the same problem. There seems to be alot of conflict between VS2005 and the SOS client.

Does anyone have a workaround for this, other than restarting the machine, which doesnt seem to work all the time.

Yes that sounds like exactly the problem. I have not looked for a pattern to reproduce it yet, although it happens regularly (not all the time though). I will pay more attention and let you know the sequence. Just going from memory, it is usually when I leave the devstudio alone overnight for exampl...

It looks as if I'm using version 6.0.31222.0

And it is located under the VC6 directory structure. My guess is I'm using the incorrect version?

Oh, and yes, I am using the 4.2 Client. I believe our server (installed in a different city) is version 3.5 or around there.

Often when I connect to a regular (non web) project from our SOS server (it's using the old 3.5 server I believe), with Visual Studio 2005, I am unable to open the SOS client itself, it just hangs and I have to kill the task. This is resolved by shutting down the VS 2005 dev environment, and then I ...