Moreover, source control has other benefits aside from recovery and reversion that neither snapshots or any other mechanism provide. But in my experience snapshots themselves get lost, corrupted, or simply fail to restore. That’s what snapshots are for, you say? Yes, maybe. If you’ve ever tried to go back to an earlier version of an Xcode project or undo some change from last week, and ended up with a headache, you’ll know what I’m talking about. However, these mechanisms do not work well with Xcode due to the complex and deep links between files in an Xcode build. Recovering or reverting a document are mechanisms Apple has put a lot of time and effort into since Lion first appeared (changes I haven’t always been a fan of…). In most normal applications, ‘Command-S’, Versions, Time Machine or other back up will save your hide when you either lose a document or realise a whole bunch of recent changes are something of a disaster. In this post we’ll look at the ‘why’ and the ‘how’ of adding source control to an existing project.
WESTERN FINANCE HOW TO
Setting up source control is easy when you create a new project (just tick the box in the project set up window), but figuring out how to add it to projects you’ve already created is a bit more challenging. If you’re not yet using source control with your Xcode projects, it’s something you want to seriously consider before a project you’re working on hits serious trouble.
0 kommentar(er)
