Comments on: Xcode 3 Feature: Version Control Repository Access

By: Anonymous

Anonymous — Sat, 19 Dec 2009 21:05:43 +0000

Can anyone recommend the top performing Remote Management tool for a small IT service company like mine? Does anyone use Kaseya.com or GFI.com? How do they compare to these guys I found recently: N-able N-central system network
? What is your best take in cost vs performance among those three? I need a good advice please... Thanks in advance!

By: Anonymous

Anonymous — Sun, 13 Dec 2009 00:36:39 +0000

i'm gonna make my own site about it

By: Nick

Nick — Wed, 25 Feb 2009 01:22:00 +0000

Cheers for this.

By: Mark

Mark — Thu, 05 Feb 2009 19:46:00 +0000

Andrew,

In my experience, Xcode's SCM features won't work unless you import the project and check out the files in the project.

You can try what you suggested (create an empty repository folder, create a project in that folder, and add the files to the repository). If it works, let me know. It would be nice to know that you don't have to import a project to use Xcode's SCM features.

By: AndrewC

AndrewC — Thu, 05 Feb 2009 15:44:00 +0000

Is it really necessary to checkin and checkout the project?

You should just be able to set up an empty repository folder and create a new project in that folder and simply add all the files to the repository from there.

By: Mark

Mark — Thu, 22 Jan 2009 20:07:00 +0000

I’ve never tried to import a project that contained files from a second project. If the import doesn’t work right, I can think of two possible solutions. If you want to place the second project under version control, import that project and check out its files. If you don’t want the second project to be under version control, make copies of the files that belong to the first project and add those copies to the first project.

You can’t create tags and branches in Xcode. You must launch the Terminal and run the appropriate commands. If you do a Google search for Subversion, the first result is the Subversion official site. On that site is an online book that contains a chapter on merging and branching that also covers tags.

By: Anonymous

Anonymous — Thu, 22 Jan 2009 10:13:00 +0000

Thank you for your writings. Still have some questions.
How do you handle a project with a set of files from a second project?

How do you create tag's and branches?

Thank you

By: Mark

Mark — Tue, 15 Jan 2008 00:44:00 +0000

For anyone having the new repository grayed out in the SCM repository menu, a grayed out repository means the project file has not been checked out of the repository. When you check out an Xcode project (Step 5), there are two copies of your Xcode project: the one you created in Xcode and the one you checked out. Make sure you open the Xcode project file you checked out, not the project file you created in Xcode.

By: Tom

Tom — Mon, 14 Jan 2008 23:23:00 +0000

Never mind, found my own answer. Apparently this is a common problem. For my simple application, the easy solution was to move the .xcodeproj file for the project down into the “trunk” subdirectory along with the source code. Then basically all work gets done inside “trunk”, and Xcode’s “build” directory gets created there. There are more sophisticated discussions of this problem and solutions on other blogs (e.g. “I Should Be Coding”).

By: Tom

Tom — Mon, 14 Jan 2008 22:11:00 +0000

Mark, thanks for the clear instructions. I followed them but hit a snag at step 6: in the SCM repository pulldown menu, my new repository is listed, but it’s gray and unselectable. Any suggestions for what I might have done wrong?