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

Migrating Visual Studio solutions/projects from .NET 1.1 to 2.0

From: Mogens Heller Jensen <mogens_at_mookid.dk>
Date: 2006-11-01 13:36:59 CET

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 Wed Nov 1 13:59:24 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.