将我所有的Visual Studio项目转移到svn的最佳方法是什么? [英] What is the best way to transfer all my Visual Studio projects to svn?

查看:217
本文介绍了将我所有的Visual Studio项目转移到svn的最佳方法是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

直到现在有一​​个名为DEVELOPMENT的磁盘文件夹.

Until now there is a disk folder named DEVELOPMENT.

此文件夹包括一个名为_LIB的顶级文件夹,其中包含公用库和层(DAL项目,业务层项目等).

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.

还有一个RESOURCES文件夹,其中有我常用的一些常见位图.

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

在此_LIB文件夹之外,还有类似于我们业务各个领域的文件夹.

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

与引用编译的dll相比,域项目遵循引用_LIB项目.

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

我需要在svn的责任下转移他们.

I need to transfer them under svn responsibility.

我想从VisualSVN服务器Ankhsvn和TortoiseSVN开始.所有这些都已安装,并且我一直在与它们一起玩了一段时间,但对于此举的总体策略,我感到困惑.

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

-要排除的内容和要包括的内容. -如何处理外部项目参考. e.t.c

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

其他信息:

阅读更多内容后,我想到了这个,我需要您的评论:

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

步骤:

  • 首先创建存储库,然后从TortoiseSVN导入我想要的任何内容.这样可以确保只有忽略的乌龟列表才处于活动状态,从而允许我导入以回购几乎所有东西.

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

对于每天使用INSIDE的项目,我将使用AnkhSVN.它将使我的解决方案远离bin,obj和我不需要的其他SCC API文件.

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.

-对于VS以外的任何其他产品,我将使用TortoiseSVN.

-For anything outside VS i will use TortoiseSVN.

推荐答案

在我们的项目中,我们使用"stantdard-结构" trunkbranchestags.运作良好,并且正式与svn一起工作的新团队成员迅速了解了结构和使用方式".

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.

所有主项目"(您的域?)都具有此结构.我们也有一些lib文件夹(像您一样)在服务器上(目前没有trunk,...).每个团队成员都必须检出lib文件夹以及工作所需的trunkbranches.

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.

如果您使用Tortoise或ankhsvn进行更改,通常是出于个人喜好.

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.

这篇关于将我所有的Visual Studio项目转移到svn的最佳方法是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆