Visual Source Safe
-
Ryan Binns wrote:
If you do use it, do backups every few seconds, as it will randomly corrupt its own database and you'll lose all your data...
Rubbish - I have used VSS for years. If this is your experience, you're doing it wrong. VSS is not perfect ( using it over a modem is hell ), but I've NEVER lost data from a VSS database. Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog
Hmm. I'll take the middle ground between you, Ryan, and Jeremy. VSS is reasonably safe, as long as you take certain precautions: - Never put your SourceSafe data base on a FAT32 partition. Always put it on an NTFS partition. - Run the Analyze tool nightly. The earlier you catch a DB problem, the easier it will be to correct. - Do not use the SourceSafe Admin backup/restore facilities unless you are willing to do a test restore on each and every backup you make. The backup has a number of well-known silent failure modes that create invalid backups that cannot be restored, even partially. - Whenever users complain that SourceSafe is checking out the wrong file, or they can't find a file they checked out, look in their SS.INI file. Visual Studio and/or SourceSafe have an awful tendency to override working directory settings, which causes check-ins/outs to happen in the wrong place. We have a policy that each user has a single folder that is the working folder for the top level project, and everything underneath matches the VSS project structure.
Software Zen:
delete this; -
toxcct wrote:
Ankh SVN
Uhm... I tried it a while ago and it didn't work, in VS05 at least. I was unable to connect to the repository or something like that. Do you know anything else? _____________________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA] - Developing ScrewTurn Wiki 1.0 Beta... -- modified at 9:01 Wednesday 5th July, 2006
It's been working fine for me for well over a month now.
"You have an arrow in your butt!" - Fiona:cool:
Welcome to CP in your language. Post the unicode version in My CP Blog [ ^ ] now.People who don't understand how awesome Firefox is have never used CPhog[^]CPhog. The act of using CPhog (Firefox)[^] alone doesn't make Firefox cool. It opens your eyes to the possibilities and then you start looking for other things like CPhog (Firefox)[^] and your eyes are suddenly open to all sorts of useful things all through Firefox. - (Self Quote)
-
Hi CPians, My department contemplates buying VSS as source control tool. What do you think about it, and what would you see as the best source control tool ? ~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
I've always found it illuminating that MS doesn't use it internally.
-
My one is TortoiseCVS + CVSNT. I'm thinking to pass to SVN but I don't know if it's much better. I've some comparission chart that has't convinced me. Have you worked with both systems adn you prefer SVN? Marc Soleda ... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
I worked with cvs and it was too buggy and didn't have basic features I needed, but I didn't have a choice because when I got to the company they were already using cvs and wouldn't change it in another company I got to chosse so I gave svn a try, th only thing I am sorry is that I didn't use all the features of it.. it works very well and worth switching from cvs
-
Rage wrote:
what would you see as the best source control tool ?
This question should be in the CP faq or something, its discussed so many times here :-D My favorite is TortoiseSVN + Subversion :cool:
**You know you're obsessed with computer graphics when you're outside and you look up at the trees and think, "Wow! That's spectacular resolution!"
Only kings, presidents, editors, and people with tapeworms have the right to use the editorial "we."**
-
Christian Graus wrote:
I don't think CVS rewards the learning curve as C++ does tho.
I still haven't used it. Although, I think I'm gonna give perforce a go. My main thing is I want VS integration; I've been too spoiled by it. Jeremy Falcon
If you want Visual Studio integration, try SVN with AnkhSVN[^], and don't forget TortoiseSVN[^] for your Windows Explorer. I've never looked back on my VSS days ever again. "Democracy is two wolves and a sheep voting on what to have for dinner" - Ross Edbert Sydney, Australia
-
Hi CPians, My department contemplates buying VSS as source control tool. What do you think about it, and what would you see as the best source control tool ? ~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
I use Perforce...it is too good.
-
hehe yeah. Even uninstalling Ankh is a mission. They tell you to reset the VS environment which basically nukes all your other settings too. Not the greatest add-in for VS ever made. regards, Paul Watson Ireland FeedHenry needs you
eh, stop bugging me about it, give it a couple of days, see what happens.
Uninstallation of add-ins is a nightmare. We regularly get emails complaining of the IDEs toolbar/control bar layout being reset when one of ours is uninstalled, despite the fact that we don't actually touch the IDE window config at all during uninstallation. Basically the IDE mucks it all up for you, regrdless of what you do... Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
Hi CPians, My department contemplates buying VSS as source control tool. What do you think about it, and what would you see as the best source control tool ? ~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
We switched from VSS to Perforce and never regretted it. The Perforce integration feature can migrate your code changes forward to another version which is usefull when you are supporting several versions of your product. We make a change in the earliest version and let Perforce integrate the changes automagically into the later versions. Also, multiple developers can work on the same code at the same time which most Version Control Systems boast but, using VSS we had to implement policy to not allow multiple checkouts of the same code because VSS constantly screwed it up. My only gripe is Perforce is slow when it needs to update its local data from the server. Stay away from VSS if you can...
-
Uninstallation of add-ins is a nightmare. We regularly get emails complaining of the IDEs toolbar/control bar layout being reset when one of ours is uninstalled, despite the fact that we don't actually touch the IDE window config at all during uninstallation. Basically the IDE mucks it all up for you, regrdless of what you do... Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
VSS has been good for us, we are working with VB6, VB.NET, and still with VB3....:-D
-
Hi CPians, My department contemplates buying VSS as source control tool. What do you think about it, and what would you see as the best source control tool ? ~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
You'll get lots of opinions about the best source control system, but I suspect nearly unanimous opinion about the worst one. VSS sucks. It stinks. It reeks. It smells of liquid, cringing, feculent death. Microsoft bought it for cheap, did a slapdash implementation to drop it into Studio, and ran away from it. The company that always eats their own dogfood doesn't use this steaming pile - they use a tweaked version of perforce (although I suspect they'll be rolling up to Team Studio). Read this page, and decide: http://www.subversionary.org/propaganda/why-not-vss Or just read this: http://support.microsoft.com/kb/q133054/ Team System might be a good choice. TortoiseSVN is an excellent choice. SourceGear vault is highly regarded. CVS is fine if you have propeller heads on staff. You would be better off entrusting your source code to a monkey with ADD and a bag of cocaine than using VSS at this point- it may have been suitable in 1995, before WANs and decent sized networking (and windows 95) but it is roadkill by any reasonable standard today. VSS is garbage, unrefined trash, and should never be used. X|
-
Hi CPians, My department contemplates buying VSS as source control tool. What do you think about it, and what would you see as the best source control tool ? ~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Hi, if you like corrupted databases, slow processing (file based db), and some other disadvantages, you should use VSS. We've tested the new "team foundation server" resp. the source code control system and are not convinced that's it good enought. So it was no problem to convince my boss and my team that we should use SUBVERSION (www.tigris.org) and TortoiseSVN. Of course under Linux ;-) but it runs also under Windows, so it's your choice. In my former company we used this combination, too - in a 7 GB repository. With no hassle, no probs, just fast and stable. Best regards Christian
-
Rage wrote:
what would you see as the best source control tool ?
This question should be in the CP faq or something, its discussed so many times here :-D My favorite is TortoiseSVN + Subversion :cool:
**You know you're obsessed with computer graphics when you're outside and you look up at the trees and think, "Wow! That's spectacular resolution!"
Only kings, presidents, editors, and people with tapeworms have the right to use the editorial "we."**
-
You'll get lots of opinions about the best source control system, but I suspect nearly unanimous opinion about the worst one. VSS sucks. It stinks. It reeks. It smells of liquid, cringing, feculent death. Microsoft bought it for cheap, did a slapdash implementation to drop it into Studio, and ran away from it. The company that always eats their own dogfood doesn't use this steaming pile - they use a tweaked version of perforce (although I suspect they'll be rolling up to Team Studio). Read this page, and decide: http://www.subversionary.org/propaganda/why-not-vss Or just read this: http://support.microsoft.com/kb/q133054/ Team System might be a good choice. TortoiseSVN is an excellent choice. SourceGear vault is highly regarded. CVS is fine if you have propeller heads on staff. You would be better off entrusting your source code to a monkey with ADD and a bag of cocaine than using VSS at this point- it may have been suitable in 1995, before WANs and decent sized networking (and windows 95) but it is roadkill by any reasonable standard today. VSS is garbage, unrefined trash, and should never be used. X|
TimHHowland wrote:
You'll get lots of opinions about the best source control system, but I suspect nearly unanimous opinion about the worst one. VSS sucks. It stinks. It reeks. It smells of liquid, cringing, feculent death.
Have you tried PVCS Dimensions? VSS is heaven in comparison. Of course I use TortoiseSVN. TortoiseSVN even works on Windows Vista x64 Beta 2.
-
TimHHowland wrote:
You'll get lots of opinions about the best source control system, but I suspect nearly unanimous opinion about the worst one. VSS sucks. It stinks. It reeks. It smells of liquid, cringing, feculent death.
Have you tried PVCS Dimensions? VSS is heaven in comparison. Of course I use TortoiseSVN. TortoiseSVN even works on Windows Vista x64 Beta 2.
I have. We rolled it out and tried to get our devs to use it. Every time we shipped a server with PVCS out to a remote office, they'd reformat it and use it to host MP3s. The one saving grace of PVCS Dimensions was it's enormous infrastructure, price tag, army of winged monkeys that you had to rent from PVCS to get it to do anything useful, and complete and utterly unusable user interface. This meant that app wasn't able to get a foothold in anywhere but the largest cube farms, where users had low expectations of their quality of life anyway. It was so obviously useless that nobody ever really used it after they spent their million bucks on the implementation. VSS was far more harmful- it was distributed essentially for "free", so thousands of shops adopted it, relied on it, and put their most precious assets into it. It's like giving machetes out to elementary school students. Microsoft should be ashamed for shipping that piece of dangerous crap for so many years, and not even using it themselves. Pathetic.