From: Matteo Tontini <il_matte_at_yahoo.it>
Date: Mon, 28 Jan 2008 16:14:36 +0000 (GMT)
I'm writing to ask suggestions about how to manage our particular project structure.
We're developing with C# and Visual Studio 2005 professional.
We have a big solution made up of several groups of projects.
Different developers work on different sets of projects, organized in solutions that realize partitions
of the global solution.
In practice we're using the 'Partitioned single solution' model as illustrated in the following article:
The problem is that our versioning system is Subversion.
With Subversion we've not been able to checkout partially the content of the root folder of the
If I want to work with a partial solution and I want to checkout only the solution file I need, and the related projects' dirs I'm forced to checkout each separate project directory by itself.
Let's see an example:
If I want to work with partitionedSolution1.sln, that is made up of project1 and project2 I have two kind of problems:
- I have to checkout separately project1Dir and project2Dir in 2 subdirectories of my working copy.
But in this way I cannot commit or update globally the content of my working copy, I'm supposed to commit and
update all the projects separately, instead.
- I cannot checkout single files. So, if I want the partitionedSolution1.sln file, the only thing I can do is to
checkout only the top folder just to get all the solution files instead of only the one I need.
Using externals doesn't allow users to easily add projects to subversion in the correct root folder
Do someone know how can I workaround this behaviors of Subversion or how can I change the structure of my Application, having in mind the need for a partitioned-solution-like structure?
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html
This is an archived mail posted to the Subversion Users mailing list.