3 ms·
I'm still using VSS as it's been 7 years and counting with no problems and I guess I'm feeling like "if it aint broke don't fix it". I'm aware that many people
by lupin_sansei 17y ago
I'm still using VSS as it's been 7 years and counting with no problems and I guess I'm feeling like "if it aint broke don't fix it". I'm aware that many people have corruption issues with VSS, so I do hourly backups, but almost a decade in it's been good enough for me not to care too much about looking for a new source control system.
Also there is a new version of VSS for Visual Studio 2005 (VSS 2005) that seems to have fixed some issues that some people have had.
- StrawberryFrog 17y agoif it aint broke don't fix it With VSS, that's a bit like saying "if my unsafe vehicle hasn't failed while driving yet, let's just keep going".
- weaksauce 17y agoIf you are not opposed to closed source stuff you should have a look at Vault(1). I migrated us over at the job that used VSS and it was a better experience. Tight integration with visual studio and works similar to VSS without all the corruption, non atomic commits, etc. Whatever road you choose make sure to back it up because no system is infallible. (see the snow leopard user destroying data bug if you need to remind yourself of that.) 1. http://www.sourcegear.com/vault/ http://www.sourcegear.com/vault/
- lupin_sansei 17y agoYep I'm doing hourly backups, plus weekly backups stored offsite.