The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Visual SourceSafe is the bane of my existence
VThornheart
Registered User regular
Registered User regular
Okay, so I've been saying for a few years that we should switch from VSS to a different repository system. We haven't taken the time to do so, and now I'm in a bit of a bind.
First and foremost, anyone who's gut instinct is to say "you should have been using _____", know in advance that I agree with you entirely. VSS was a poor decision from the day it was decided, but I had little choice when that was first decided for our source control years ago. I have much more influence now in the decision making process, and my first priority is to change to a more stable system like Subversion. So know that I agree with you and I'm just trying to resolve this temporary situation that has come up.
That being said, here's the current issue. As is par for the course with VSS, one of the VSS databases has apparently become corrupted. I'm about halfway through the analyze utility's process right now (56% on step 2 of 4), but it's taking forever, and I'd like to open my Visual Studio 2005 projects that connect to this VSS system and work with them offline.
The problem with this appears to be twofold, however. The first is that apparently connecting to or using the VSS database at all while analyze is being run is a very, very bad thing. The second is that the Visual Studio IDE is using VSS through the integrated plug-in, and so (I assume) VSS is being connected to whenever the projects are opened.
I attempted to perform the following procedure to disable use of VSS:
http://msdn2.microsoft.com/en-us/library/axafab5c(VS.80).aspx
However when I did so and I opened a project that usually connects to a different VSS database, opening that project seems to have re-enabled the VSS plugin all on its own.
After looking around and only finding this as a resource, I figured I'd make an appeal to the community at large... is there some sort of change, even a manual one, that I can do to make sure that my projects won't attempt to connect to the VSS database when I open them? I can see some references to "source control" in the Solution file, but there's no reference to the actual VSS database in there, leading me to believe that the actual connection information is *somewhere* else (and I have no idea where). I'll be opening files manually right now to try and find where the connection information is being stored, but I figured there might be someone in here who already knows and can save some potential pain in this area.
TL;DR
I need to stop one of my Visual Studio projects from automatically connecting to our Visual SourceSafe repository, but I have no idea where to look. I'll eventually find it manually, but there seems to be dozens of very large files that I'm going to have to comb through to find it manually (and when I do find it, I'm not sure that if I change it manually it will negatively effect the project), so if anyone knows off the top of their head I'll buy you a beer at PAX.
EDIT: In other news, I wanted to add this (since it's the help and advice forum) in case someone comes here looking for advice on what Source Control software to use and stumbles into this thread. Don't make the mistake we did. Don't use Visual SourceSafe, for the love of all that is holy and good.
EDIT 2: Okay, I found the connection information in several .scc files. There's many of them (one in each folder), but I guess it won't do any harm to rename or temporarily remove them and then give it a shot. There's two .scc files in each folder however, and one of them appears to have binary data and thus I'm at a loss to edit manually. I don't think I want to take any chances, so I'm just going to remove both of these .scc files and put them back after this is all resolved. Hmm... well, here's hoping.
First and foremost, anyone who's gut instinct is to say "you should have been using _____", know in advance that I agree with you entirely. VSS was a poor decision from the day it was decided, but I had little choice when that was first decided for our source control years ago. I have much more influence now in the decision making process, and my first priority is to change to a more stable system like Subversion. So know that I agree with you and I'm just trying to resolve this temporary situation that has come up.
That being said, here's the current issue. As is par for the course with VSS, one of the VSS databases has apparently become corrupted. I'm about halfway through the analyze utility's process right now (56% on step 2 of 4), but it's taking forever, and I'd like to open my Visual Studio 2005 projects that connect to this VSS system and work with them offline.
The problem with this appears to be twofold, however. The first is that apparently connecting to or using the VSS database at all while analyze is being run is a very, very bad thing. The second is that the Visual Studio IDE is using VSS through the integrated plug-in, and so (I assume) VSS is being connected to whenever the projects are opened.
I attempted to perform the following procedure to disable use of VSS:
http://msdn2.microsoft.com/en-us/library/axafab5c(VS.80).aspx
However when I did so and I opened a project that usually connects to a different VSS database, opening that project seems to have re-enabled the VSS plugin all on its own.
After looking around and only finding this as a resource, I figured I'd make an appeal to the community at large... is there some sort of change, even a manual one, that I can do to make sure that my projects won't attempt to connect to the VSS database when I open them? I can see some references to "source control" in the Solution file, but there's no reference to the actual VSS database in there, leading me to believe that the actual connection information is *somewhere* else (and I have no idea where). I'll be opening files manually right now to try and find where the connection information is being stored, but I figured there might be someone in here who already knows and can save some potential pain in this area.
TL;DR
I need to stop one of my Visual Studio projects from automatically connecting to our Visual SourceSafe repository, but I have no idea where to look. I'll eventually find it manually, but there seems to be dozens of very large files that I'm going to have to comb through to find it manually (and when I do find it, I'm not sure that if I change it manually it will negatively effect the project), so if anyone knows off the top of their head I'll buy you a beer at PAX.
EDIT: In other news, I wanted to add this (since it's the help and advice forum) in case someone comes here looking for advice on what Source Control software to use and stumbles into this thread. Don't make the mistake we did. Don't use Visual SourceSafe, for the love of all that is holy and good.
EDIT 2: Okay, I found the connection information in several .scc files. There's many of them (one in each folder), but I guess it won't do any harm to rename or temporarily remove them and then give it a shot. There's two .scc files in each folder however, and one of them appears to have binary data and thus I'm at a loss to edit manually. I don't think I want to take any chances, so I'm just going to remove both of these .scc files and put them back after this is all resolved. Hmm... well, here's hoping.
3DS Friend Code: 1950-8938-9095
VThornheart on
0
Posts
Anyways, feel free to lock this thread.