![]() ![]() It also goes into some of the questions I asked myself about source code structure of shared components in the face of online repositories like GitHub. This article then is my journey on how I finally shook off the shackles of SourceSafe whilst maintaining as much history as possible. ![]() Mainstream support ended for SourceSafe last year so I don’t even have that to prop me up any longer either. This wasn’t because of any killer feature, but mostly because I didn’t want to lose easy access to my ever growing archive of version history when switching to another product. Given that it was also the VCS product I had been using at my client back then I got training and experience as a nice by-product of work.įast forward 15 years and I still find myself using the same VSS repo I set up all those years ago! Despite a considerable number of excellent free and open source alternatives springing up in the intervening years that were far superior, I found myself clinging on. Unsure about exactly which product to choose I naturally fell into using the one that came bundled with the compiler – Visual SourceSafe (VSS). Having been brought up to use a Version Control System (VCS) to manage my source code assets at work it seemed eminently sensible to do the same thing at home. Chris Oldwood records the trials and triumphs of migrating from VSS to git.īack in the late 1990s I found myself starting to acquire a considerable volume of code from various personal projects that I had been working on in my spare time. ![]() Migrating from one version control system to another is a big change. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |