News for hackers. Stuff that matters.
Re:How Microsoft Office Moved from Source Depot to Git by BobbyTables2 on Wednesday June 11, 2025 @11:23PM (#44254030)
I’d like to know when Microsoft internally migrated away from Visual SourceSafe…

They should have recalled it to avoid continued public use…

Re:How Microsoft Office Moved from Source Depot to Git by dshacker on Wednesday June 11, 2025 @11:32PM (#44254067)
I didn't even know Microsoft SourceSafe existed.
Re:How Microsoft Office Moved from Source Depot to Git by masklinn on Thursday June 12, 2025 @12:49AM (#44254393)
Lucky you. Definitely one of the worst tools I’ve had the displeasure of working with. Made worse by people building on top of it for some insane reason.
Re:How Microsoft Office Moved from Source Depot to Git by TowerTall on Thursday June 12, 2025 @03:37AM (#44255045)
I remember when we migrated from Visual Source Safe to TFS at my place of work. I was in charge of the migration and we hit errors and opened a ticket with Microsoft Premier Support. The ticket ended up being assigned to one of creators of Source Safe who replied "What you are seeing is not possible". He did manage to solve it in the end after a lot of head scratching.
Re:How Microsoft Office Moved from Source Depot to Git by mickeyp on Thursday June 12, 2025 @03:35AM (#44255037)
Agreed. It had a funny habit of corrupting its own data store also. That's absolutely what you want in a source control system.

It sucked; but honestly, not using anything is even worse than SourceSafe.

Re:How Microsoft Office Moved from Source Depot to Git by masklinn on Thursday June 12, 2025 @04:01AM (#44255163)
> Agreed. It had a funny habit of corrupting its own data store also. That's absolutely what you want in a source control system.

I still ‘member articles calling it a source destruction system. Good times.

> It sucked; but honestly, not using anything is even worse than SourceSafe.

There have always been alternatives. And even when you didn’t use anything, at least you knew what to expect. Files didn’t magically disappear from old tarballs.

Re:How Microsoft Office Moved from Source Depot to Git by moron4hire on Thursday June 12, 2025 @02:04AM (#44254685)
It was at least a little better than CVS, but with SVN available at the same time, never understood the mentality of the offices that I worked at using Source Safe instead of SVN.
Re:How Microsoft Office Moved from Source Depot to Git by masklinn on Thursday June 12, 2025 @03:19AM (#44254966)
> It was at least a little better than CVS

Highly debatable.

CVS has a horrendous UI, but didn’t have a tendency to corrupt itself at the drop of a hat and didn’t require locking files to edit them by default (and then require a repository admin to come in and unlock files when a colleague went on holidays with files checked out). Also didn’t require shared write access to an SMB share (one of the reasons it corrupted itself so regularly).

Re:How Microsoft Office Moved from Source Depot to Git by moron4hire on Friday June 13, 2025 @02:16AM (#44266133)
Uhh, CVS definitely regularly corrupted itself. I nearly lost my senior research thesis in undergrad because of it. The only thing that saved me was understanding professors and the fact that I could drive back home to my parents' house and get back to my review in 30 minutes, where I had a good copy of my code I could put on an Iomega Zip disk from my desktop instead of the corrupted copy we couldn't pull from CVS in the CS lab.
Re:How Microsoft Office Moved from Source Depot to Git by codeulike on Thursday June 12, 2025 @04:04AM (#44255180)
We used it. We knew no better. It was different then, you might not hear about alternatives unless you went looking for them. Source Safe was integrated with Visual Studio so was an obvious choice for small teams.

Get this; if you wanted to change a file you had to check it out. It was then locked and no-one else could change it. Files were literally read only on your machine unless you checked them out. The 'one at a time please' approach to Source Control (the other approach being 'lets figure out how to merge this later')

Re:How Microsoft Office Moved from Source Depot to Git by namdnay on Thursday June 12, 2025 @05:11AM (#44255541)
I remember a big commercial SCM at the time that had this as an option, when you wanted to make sure you wouldn’t need to merge. Can’t remember what it was called, you could “sync to file system” a bit like dropbox and it required teams of full time admins to build releases and cut branches and stuff . Think it was bought by IBM?
Re:How Microsoft Office Moved from Source Depot to Git by robin_reala on Thursday June 12, 2025 @07:37AM (#44256456)
I guess you’re talking about Rational Rose? I had the misfortune of using that at my first industry job (fintech in 2004).
Re:How Microsoft Office Moved from Source Depot to Git by meepmorp on Thursday June 12, 2025 @04:05PM (#44262544)
Rose is a UML modeling tool
Re:How Microsoft Office Moved from Source Depot to Git by robin_reala on Thursday June 12, 2025 @05:11PM (#44263247)
Oops, it was ClearCase that was Rational’s SCM: https://en.wikipedia.org/wiki/IBM_DevOps_Code_ClearCase
Re:How Microsoft Office Moved from Source Depot to Git by becurious on Thursday June 12, 2025 @11:45AM (#44259093)
ClearCase?
Re:How Microsoft Office Moved from Source Depot to Git by rswail on Thursday June 12, 2025 @05:18AM (#44255581)
Which is exactly how CVS (and its predecessors RCS and SCCS) worked.

They were file based revision control, not repository based.

SVN added folders like trunk/branches/tags that overlaid the file based versioning by basically creating copies of the files under each folder.

Which is why branch creation/merging was such a complicated process, because if any of the files didn't merge, you had a half merged branch source and a half merged branch destination that you had to roll back.

Re:How Microsoft Office Moved from Source Depot to Git by umanwizard on Thursday June 12, 2025 @08:00AM (#44256694)
I am quite sure that you can edit files in an svn repo to your heart’s content regardless of whether anyone else is editing them on their machine at the same time.
Re:How Microsoft Office Moved from Source Depot to Git by masklinn on Thursday June 12, 2025 @10:27AM (#44258224)
Yep, svn has a lock feature but it is opt-in per file (possibly filetype?)

A pretty good tradeoff, because you can set it on complex structured files (e.g. PSDs and the like) to avoid the ballache of getting a conflict in an unmergeable file but it does not block code edition.

And importantly anyone can steal locks by default. So a colleague forgetting to unlock and going on holidays does not require finding a repo admin.

Re:How Microsoft Office Moved from Source Depot to Git by fanf2 on Thursday June 12, 2025 @05:46AM (#44255737)
CVS was called the “concurrent version system” because it did not lock files on checkout. Nor did svn. Perforce does.
Re:How Microsoft Office Moved from Source Depot to Git by rswail on Thursday June 12, 2025 @09:58AM (#44257899)
True dat, my mistake. That was its major feature, from memory though it still used the same reversed diff file format?
Re:How Microsoft Office Moved from Source Depot to Git by ack_complete on Thursday June 12, 2025 @10:33AM (#44258276)
Perforce does not lock files on checkout unless you have the file specifically configured to enforce exclusive locking in the file's metadata or depot typemap.
Re:How Microsoft Office Moved from Source Depot to Git by pjc50 on Thursday June 12, 2025 @05:43AM (#44255726)
The lock approach is still used in IC design for some of the Cadence/Synopsis data files which are unmergable binaries. Not precisely sure of the details but I've heard it from other parts of the org.
Re:How Microsoft Office Moved from Source Depot to Git by dagw on Thursday June 12, 2025 @08:21AM (#44256906)
A lot of engineering is the same. You cannot diff and merge CAD files, so you lock them.
Re:How Microsoft Office Moved from Source Depot to Git by malkia on Thursday June 12, 2025 @11:10AM (#44258723)
Similar in video game shops - lots of binary files, or even huge (non-editable by human) text ones.
Re:How Microsoft Office Moved from Source Depot to Git by Disposal8433 on Thursday June 12, 2025 @07:15AM (#44256299)
The file lock was a fun feature when a developer forgot to unlock it and went on holidays. Don't forget the black hole feature that made files randomly disappear for no reason. It may have been the worst piece of software I have ever used.
Re:How Microsoft Office Moved from Source Depot to Git by qingcharles on Thursday June 12, 2025 @05:01AM (#44255482)
It was pretty janky. We used it in the gamedev world in the 90s once the migration to Visual C started.
Re:How Microsoft Office Moved from Source Depot to Git by pianoben on Thursday June 12, 2025 @12:37AM (#44254359)
I don't know that they ever used it internally, certainly not for anything major. If they had, they probably wouldn't have sold it as it was...

Can't explain TFS though, that was still garbage internally and externally.

Re:How Microsoft Office Moved from Source Depot to Git by RandallBrown on Thursday June 12, 2025 @12:39AM (#44254366)
I doubt most teams ever used it.

I spent a couple years at Microsoft and our team used Source Depot because a lot of people thought that our products were special and even Microsoft's own source control (TFS at the time) wasn't good enough.

I had used TFS at a previous job and didn't like it much, but I really missed it after having to use Source Depot.

Re:How Microsoft Office Moved from Source Depot to Git by RyJones on Thursday June 12, 2025 @01:12AM (#44254484)
USGEO used it in the late 90s, as well as RAID
Re:How Microsoft Office Moved from Source Depot to Git by jbergens on Thursday June 12, 2025 @04:47AM (#44255414)
I was surprised that TFS was not mentioned in the story (at least not as far as I have read).

It should have existed around the same time and other parts of MS were using it. I think it was released around 2005 but MS probably had it internally earlier.

Re:How Microsoft Office Moved from Source Depot to Git by canucker2016 on Thursday June 12, 2025 @05:08AM (#44255526)
SLM (aka slime, shared file-system source code control system) was used in most of MS, aka systems & apps.

NT created (well not NT itself, IIRC, there was some an MS-internal developer tools group in charge)/moved to source depot since a shared file-system doesn't scale well to thousands of users. Especially if some file gets locked and you DoS the whole division.

Source depot became the SCCS of choice (outside of Dev Division).

Then git took over, and MS had to scale git to NT-size scale, and upstream many of the changes to git mainline.

Raymond Chen has a blog that mentions much of this - https://devblogs.microsoft.com/oldnewthing/20180122-00/?p=97...

Re:How Microsoft Office Moved from Source Depot to Git by int_19h on Thursday June 12, 2025 @12:28PM (#44259615)
TFS was used heavily by DevDiv, but as far as I know they never got perf to the point where Windows folk were satisfied with it on their monorepo.

It wasn't too bad for a centralized source control system tbh. Felt a lot like SVN reimagined through the prism of Microsoft's infamous NIH syndrome. I'm honestly not sure why anyone would use it over SVN unless you wanted their deep integration with Visual Studio.

Re:How Microsoft Office Moved from Source Depot to Git by anonymars on Thursday June 12, 2025 @07:41PM (#44264371)
After the initial TFS 1.0 hiccups, merging was way, way better than SVN. SVN didn't track anything about merges until 1.6. Even today git's handling of file names has nothing on TFS.
Re:How Microsoft Office Moved from Source Depot to Git by mattgrice on Thursday June 12, 2025 @12:39AM (#44254367)
Around 2000? The only project I ever knew that used it was .NET and that was on SD by around then.