• dan@upvote.au
    link
    fedilink
    arrow-up
    21
    ·
    edit-2
    2 days ago

    Visual SourceSafe

    Yes! That’s the one I was struggling to remember the name of. My previous employer started on Visual SourceSafe in the 90s and migrated to Team Foundation Server (TFS) in the 2000s. There were still remnants of SourceSafe when I worked there (2010 to 2013).

    I remember TFS had locks for binary files. There was one time we had to figure out how to remove locks held by an ex-employee - they were doing a big branch merge when they left the company, and left all the files locked. It didn’t automatically drop the locks when their account was deleted.

    They had a bunch of VB6 COM components last modified in 1999 that I’m 80% sure are still in prod today. It was still working and Microsoft were still supporting VB6 and Classic ASP, so there wasn’t a big rush to rewrite it.

    • HarkMahlberg@kbin.earth
      link
      fedilink
      arrow-up
      6
      ·
      2 days ago

      Welcome to my world… our new lead architect has mandated that we move everything from TFS to GitLab before the end of the year. I hope it comes true.

      • Flames5123@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        23 hours ago

        At the start of COVID, I migrated our three projects to git from VSS. I also wrote a doc for our other teams to do the same. It was amazing once we got it working. Small team of 3, but we started using feature branches which enabled us to easily merge everything into a testing branch and release only certain features at a time. So much cleaner.

        Before I left, I almost got semi automatic CI/CD working with Jenkins!

      • nogooduser@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I remember when our company split up and we had to give them the source code of some older versions that they still used. We couldn’t do that because the repo was corrupt meaning that we couldn’t access some older revisions. We had no problems using it day to day so nobody noticed which meant that all backups were also corrupted.