Where I work I have several projects in separate repositories. Each project shares a lot of common code that I want to pull out into a distinct project. I’m thinking of calling the project with the following scheme: Company.Department.Common or Company.Department.Utility.
I’ve constructed a project for this and it has an automated build script (as does every other project).
My question is that I would like to refactor my existing projects to depend on this new project. One method that is quite basic but not exactly what I am looking for is to simply build my Utility project, copy the DLL to my lib folder in my consuming project, and check that DLL in with that consuming project.
I personally feel that method is quite poor. I would like to have a reference to my Utility project and will perform a svn-update and build of the Utility project before the build of the consuming project.
FYI, the kind of code that’s in the Utlity project are Logging facilities, BDD Unit Testing classes, IoC faclities, and Common Company.Department focused classes.
Hope my question isn’t too vague, but with some answers I may be able to sharpen the focus on exactly what I would like to do.
Lastly, this is for .Net projects and using NAnt as the build script, and svn for code versioning.
Greg is right in that you will probably want to use the svn:external feature. I created a step by step guide on how to do this on Windows with TortoiseSVN. I found it quite confusing the first couple times I used it. I created the guide, so that I can look it up, because I don’t do it all the time.
Using svn:externals with Windows