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 the repository and every application project stored as a project within the same repository.

I recently switched to Subversion for source control and I fear that I did not do a good job of structuring the repository. I would like to hear what others are doing.

Answer 1

using the branch/trunk/tag repository structure is pretty standard, but if I’m understanding you properly, your issue is that you have a set of common dll projects that get used across multiple projects. This can definately become tricky to manage.

So the typical scenario here is that you have some class library called Common.Helpers that has code that is common to all your applications.

Let’s say I’m starting a new application called StackOverflow.Web that needs to reference Common.Helpers.

Usually what you would do is create a new solution file and add a new project called Stackoverflow.Web and add the existing Common.Helpers project and then reference it from the new Stackoverflow.Web project.

What I usually try and do is create a repository for the Common.Helpers project and then in subversion reference it as an external. That way you can keep the code under source control in a single location, but still use it seperately in multiple projects.