4 ms·

Subversion? Shame? I still use Visual SourceSafe.

weaksauce 17y ago
I upvoted you just for the sheer brazenness of it all. Seriously though, why? SVN won't corrupt the database and is much easier to branch/merge than sourcesafe. That being said I don't think there is anything "wrong" with using SVN. (source safe was terrible in anything other than checking out the latest code the last time I had to use it for a job.)
- deleted 17y ago
  [deleted]
- noblethrasher 17y ago
  I've been using SVN for a while but I'm pretty sure that the VSS db corruption was due to its reliance on Windows file shares.
- 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 ago
    if 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 ago
    If 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 ago
      Yep I'm doing hourly backups, plus weekly backups stored offsite.
icey 17y ago
VisualSVN + tortoise is a nice way to switch over to SVN. You just have to get bit by a VSS db corruption once to make the switch. Something to keep in mind, your database may already be corrupt and you don't know it yet so your backups could be already be poisoned.
- ja27 17y ago
  I've been through two VSS db corruptions over the years. Never again. Quite possibly the worst Microsoft product of all time. We've been on CVS for many years.
mattmcknight 17y ago
Microsoft Team Foundation Version Control (TFVC) had a nice feature- you needed a license on your server if you want to check out the code from there. I haven't used it in a while, so I don't know if that is still true. Storing everything in SQL Server is an interesting approach to selling another SQL Server license.

I upvoted you just for the sheer brazenness of it all. Seriously though, why? SVN won't corrupt the database and is much easier to branch/merge than sourcesafe. That being said I don't think there is anything "wrong" with using SVN. (source safe was terrible in anything other than checking out the latest code the last time I had to use it for a job.)

deleted 17y ago
[deleted]
noblethrasher 17y ago
I've been using SVN for a while but I'm pretty sure that the VSS db corruption was due to its reliance on Windows file shares.
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 ago
  if 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 ago
  If 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 ago
    Yep I'm doing hourly backups, plus weekly backups stored offsite.

icey 17y ago

VisualSVN + tortoise is a nice way to switch over to SVN. You just have to get bit by a VSS db corruption once to make the switch. Something to keep in mind, your database may already be corrupt and you don't know it yet so your backups could be already be poisoned.

ja27 17y ago
I've been through two VSS db corruptions over the years. Never again. Quite possibly the worst Microsoft product of all time. We've been on CVS for many years.

mattmcknight 17y ago

Microsoft Team Foundation Version Control (TFVC) had a nice feature- you needed a license on your server if you want to check out the code from there. I haven't used it in a while, so I don't know if that is still true. Storing everything in SQL Server is an interesting approach to selling another SQL Server license.