Using Subversion with Xcode 3.0. When you’re coding a huge project in Xcode, and you’ve written all of this awesome stuff, it’s almost done, and the big release is coming soon, that’s when the worst happens: The hard drive that had all of your code on it dies suddenlyYou didn’t have a backup in TimeMachineFiles become corruptedYou remove some important code, or overwrite it, accidentally – and save over your only copy; and you don’t know how you’ll ever manage to rewrite those thousands of lines of code over againAll of the above This is where Subversion (called “SVN” for short) comes in handy. What does it do? Well, in addition to storing a backup copy of your files, it is a “version control” system. This means that every time you upload a new/changed copy of something, it’s saved as a new revision of the file, not replacing the existing.
In practice, it’s not quite that simple. Fortunately, since version 1.5, Xcode has offered built-in support for Subversion. It will most likely ask for your password. Version Control with Subversion and Xcode. Getting Control with Subversion and Xcode. Xcode 5 does more than ever to help you create high-quality apps.
It automatically configures your apps to use the latest Apple services, manages images in a unified asset catalog, and helps you design stunning interfaces for iOS 7 and OS X. It also makes it easy to analyze your code, monitor performance, and test your apps, and with access to continuous integration built right in, your team can create better apps than ever before. Automatic Configuration Xcode 5 automatically configures your app to enable Apple services such as iCloud, Passbook, or Game Center, directly within the IDE. With the new capabilities editor, enabling Apple services is as easy as flipping a switch. Test Navigator Test-driven development is easier than ever with the new Test Navigator which helps you create, edit, and run unit tests. Bots for Continuous Integration Auto Layout Debug Gauges View resource consumption data at a glance, including CPU, memory, energy use, iCloud, and OpenGL ES. Source Control. Version Control in Xcode using SCM.
On Monday I shifted to Xcode SCM for visioning control and its seems to me very cool.
Before we used smartSvn but it was not that cool like the feature Xcode SCM have. So till now, I am very happy with this. So if you want to use version control for your Xcode projects then please follow the link below: If you have any question regarding setting up the repository on server or didn’t understand any step in that tutorial, then please feel free to ask me in comments. Popularity: 6% [?] Version Control is Your Friend. Most new developers, especially those with no serious intentions of becoming a professional programmer, generally think of version control software as being something that they don't need.
Heck, I resisted using it for a long time even after programming became my livelihood because on most of my projects, I was the sole developer. Concurrency just isn't an issue with one developer, right? Well, yes, that's true. But, version control is still worth using even if you're a sole developer. Putting your projects under version control gives you the ability to "undo" past the time you last opened Xcode. And, everything you need to use version control is already on your hard drive, and Xcode knows all about version control, so it's not exactly hard to use.
Note: I know a lot of people love git. Choosing a Repository Location All source control systems store their data in something called a "repository". You don't necessarily need to have your repository on a separate hard drive, however. SvnX - Downloads - Development Tools.