I'm using .NET 1.1 and 2.0 too, but i'm not really having experience with
this exact kind of stuff :-)
A fact is: when migrating from 1.1 to 2.0, it will create more files. So if
they are created in every branch (the same files), I guess it will indeed be
messy whilst merging them back because a file while have been created in the
branch and in the trunk?
How many branches do you have? I think the best thing is too copy your
project, and do some test with some solutions and branches. Maybe it will be
easy and clear, but I do think that it will be a trouble. I would merge a
maximum of the branches before doing the upgrade.
Hpe this helps :-S
Pieter
"Mogens Heller Jensen" <mogens@mookid.dk>
wrote in message news:11209.80.63.36.226.1162384619.squirrel@80.63.36.226...
> Hello users (mostly those with experience in the following: Windows,
> Visual Studio
> 2003/2005, C#/J# .NET 1.1/.NET 2.0, TortoiseSVN :o) ),
>
> I have a question regarding the migration to .NET 2.0 of a semi-large
> project
> (consisting of about 130 Visual Studio projects, and about 100 solutions
> each
> consisting of a subset of these projects):
>
> (How) is it possible to handle (in a nice way) the branches that exist in
> our
> repository when converting the projects?
>
> If anyone has experience in doing this, please let me know.
>
> Is it necessary to merge all the branches into the trunk, do the
> migration, and then
> re-branch?
>
> Or is it better to migrate the trunk, and then solve conflicts as they
> arise when
> branches need to be merged in the future?
>
> Or can we migrate the trunk and each branch, and then count on things not
> being to
> messy when we need to merge in the future?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Nov 6 10:22:39 2006