Where I work, I have several projects in separate repositories. Each project has a lot of common code, which I want to bring to a separate project. I am going to name the project with the following scheme: Company.Department.Common or Company.Department.Utility.
I built a project for this, and it has an automatic build script (like any other project).
My question is that I would like to reorganize my existing projects to depend on this new project. One method that is quite simple, but not quite what I'm looking for, is to simply create my Utility project, copy the DLL to my lib folder in my consumer project, and verify that the DLL is in this consuming project.
I personally think that the method is rather poor. I would like to have a link to my Utility project and will do the svn update and build of the Utility project before building the consumption project.
FYI, the type of code that the Utlity project includes logging tools, BDD test classes, IoC classes, and Common Company.Department classes.
I hope my question is not too vague, but with some answers I can strengthen the focus on exactly what I would like to do.
Finally, this is for .Net projects and using NAnt as a script and svn assembly for version control of the code.
source
share