What is the best way to transfer all my Visual Studio projects to svn?

1
votes

Until now there is a disk folder named DEVELOPMENT.

This folder includes a top level folder named _LIB where the common libraries and layers (DAL projects, Business Layer projects e.t.c) are included.

There is also a RESOURCES folder where i have some common bitmaps that i use (mostly).

Aside to this _LIB folder there are folders that resemble the various domains of our business.

The domain projects follow the reference _LIB projects than reference the compiled dlls.

I need to transfer them under svn responsibility.

I would like to start with VisualSVN server,Ankhsvn and TortoiseSVN. All of them are installed and i have been playing with them for a little bit, but i am confused as to the overall strategy of this move.

From what i have understood i need to have clear picture for the following aspects (which i dont have and i need help):

-What to exclude and what to include. -How to deal with the external project references. e.t.c

Additional Info:

After reading some more i came up to this and i need your comments:

Steps:

  • First create the repo and import anything i want there from TortoiseSVN. This will ensure that only the ignore list of tortoise will be active allowing me to import to repo nearly everything.

  • For every day use INSIDE a project i will use AnkhSVN. It will keep my solution clean from bin,obj and the other SCC API files that i dont need.

-For anything outside VS i will use TortoiseSVN.

1
visual-studiosvntortoisesvnankhsvn
Added some more info after some reading and tests. – e4rthdog
If the SVN plug-in that connects the IDE to SVN is doing it's job, the IDE will be the adding things to SVN via the plug-in, but it (the IDE) will decided what things need to be added and it will only add files that need to be there. – Blake7

1 Answers

1
votes

In our projects we use "stantdard-structure" with trunk, branches and tags. Works fine and new teammember who formally worked with svn understand the structure and "the way to use" quickly.

All "main-projects" (your domains?) have this structure. We also have some lib-folders (like you) which have there on place on server (at the moment without trunk, ...). Every teammember have to check out the lib folder and the trunk or branches he need for his work.

If you use Tortoise or ankhsvn to commit your changes is often a matter of taste.

Hope this helps you a little bit to "unconfuse" you. Please feel free for further enquiry.