Best way to structure a repository in Subversion for Visual Studio projects?

Question

I have a few C# .dll projects which are common to many applications. Currently, I have one big repository. I have each DLL stored as a separate project within

Answer 1

If you want to use the merge-tracking of Subversion 1.5 over more than one project at the same time you should use a single tree without externals.

A tracked merge is (just like a commit) always over a directory and its children.

The same rule applies on atomic commits. (Works only stable within a single workingcopy. It might work in some specific other cases but that behavior is not guaranteed)