RE: Partial checkout

First of all thank's a lot, David, for your answer,

actually you're right: changing the layout as you say could enhance the situation but still there would be two problems:

1)
we have different partial solutions that share some projects:
e.g., "/subproj/proj1", "/subproj/proj2", "/subproj/proj3"
were both mysln1.sln and mysln2.sln need to be in "/subproj" because both use two out of three of the projects.
So the problem is not completely fixed in this way but it is still a good enahncement because it allows us to reduce the number of unused projects in our working copies.
2)
but there is also a usability issue:
each developer should be informed about were each solution file is placed or
try to browse the repository to find it.
This could lead to not finding the solution and to create a new one elsewhere thus duplicating a solution file and some projects.

The reason why I decided to put all the solution files in the root directory is that:
because of point 1) the other choice does not provide me the perfect solution to the problem (though a very good one) then I preferred to keep all solution files immediately visible thus avoiding point 2).

Still I'm considering changing the layout but I hope Subversion 1.5 will be fast enough to solve the problem.

Matteo

"Bicking, David (HHoldings, IT)" <David.Bicking_at_thehartford.com> ha scritto:

>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:

>http://msdn2.microsoft.com/en-us/library/ms998208.aspx

>The problem is that our versioning system is Subversion.

Well, not really, but I understand what you mean.

>With Subversion we've not been able to checkout partially the content
of the root
>folder of the repository.
>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.

The next version will have "sparse folders" (or some such name) which
will allow you to check out pieces of a folder structure. This might
alleviate some of the problems.
        
>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.

You can work around this by changing the way you layout your solution's
folder structures. Each subsection that has its own solution should go
into a single folder (e.g., "/subproj/proj1", "/subproj/proj2", where
mysln.sln is in "/subproj"). The "real" solution would reference all
those together, so if there are three subsections, there will be three
"top level" folders.

>- 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.

This isn't a problem if you follow my instructions.

>Matteo

David

--
All developers are lazy as evidenced by the amount of time and effort
spent in making a computer do the work. 
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
       
---------------------------------
---------------------------------
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail