[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: .NET project source tree organization question

From: Grant Rettke <grettke_at_acm.org>
Date: 2006-09-14 23:42:07 CEST

Keeping a solution and its project under a single subversion project is
the way most people start. If you have two solutions that link against
the same project, then you will probably look at the other approach.

Quoting Jiho Han <jhan@InfinityInfo.com>:

> I am probably going to do cut over as well, not importing any VSS
> history.
> It seems to me, more and more I think about it, it makes sense to branch
> at the solution level because a solution is the end product after all.
> If any of the projects are being reused elsewhere, then I could create
> another "solution" that contains trunk, branches, and tags. And perhaps
> use the Externals concept. I'm also beginning to wonder whether it's
> really necessary to have the trios. For example, perhaps trunk could be
> eliminated since the main folder will be the "trunk".
> I have to think a bit more but sometimes you just gotta start somewhere.
> Thanks.
> -----Original Message-----
> From: Grant Rettke [mailto:grettke@acm.org]
> Sent: Thursday, September 14, 2006 3:11 PM
> To: Jiho Han
> Cc: users@subversion.tigris.org
> Subject: Re: .NET project source tree organization question
> We started from scratch, no VSS import...but still.
> We have got individual Subversion-projects for every .NET-project and
> .NET-solution. You make working copies under the same top level
> directory and everything works fine; solution project references are
> relative.
> Quoting Jiho Han <jhan@InfinityInfo.com>:
>> I am looking to move to subversion from vss as with a lot of people
>> I'm sure.
>> I've been reading the book and in it, it recommends creating trunk,
>> branches, tags folder under a project root.
>> A typical .NET project - the way I have been organizing - would
>> contain a folder for the .sln file, and each sub-folder will contain
>> projects under the solution.
>> Ex)
>> SomeCRUDApp/
>> SomeCRUDApp/SomeCRUDApp.sln
>> SomeCRUDApp/SomeCRUDApp.UI/SomeCRUDApp.UI.csproj
>> SomeCRUDApp/SomeCRUDAPP.BLL/SomeCRUDApp.BLL.csproj
>> SomeCRUDApp/SomeCRUDApp.DAL/SomeCRUDApp.DAL.csproj
>> ... and so on.
>> I am exactly at a loss how to go from this to the proposed subversion
>> structure. Would I create the trio folders under each project? Or
>> would I create the trio once under the solution folder?
>> Thanks for any pointers.
>> Jiho Han
>> Senior Software Engineer
>> Infinity Info Systems
>> The Sales Technology Experts
>> Tel: 212.563.4400 x6375
>> Fax: 212.760.0540
>> jhan@infinityinfo.com
>> www.infinityinfo.com <http://www.infinityinfo.com/>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 14 23:42:52 2006

This is an archived mail posted to the Subversion Users mailing list.