Microsoft OneDrive for Business modifies files as it syncs
SharePoint has always been a piece of garbage. Unfortunately it's a <i>money making</i> piece of garbage, so there you go.<p>Inside MS, SharePoint is often used to "track" project documents. Start a project and -poof- your most unfavorite PM has creates a procrustean bed of document folders, all set for you to lose your documents in because none of the categories match anything in the actual product. Like, having whole separate doc folders for Beta 1 and Beta 2 (there's going to be a second beta, and the docs are going to be cloned into those? Really?)<p>PMs: "Please add your documentation to these folders."<p>Devs: "When we do that, we lose control of the documents, we can't get at the history, we can't search them, we can't even <i>find</i> stuff in there, and SharePoint is slow and the permissions are always wrong, and a year after the project ships the SharePoint will be destroyed and we will lose all of the documentation." [All of this is true, especially the bit about not very old project documentation completely going away, OMFG].<p>PMs: "We don't care."<p>Devs: [check documents into the source tree anyway, and write a mirroring script to copy the things to SharePoint]<p>PMs: "Stop that."<p>Devs: "We don't care."<p>The right answer is, of course, to fire the damned PMs who serially insist on a crappy excuse for a version control system despite everyone else pushing back and saying that it sucked hard. Only saw that happen a couple of times.