适用于小型团队的 Visual Studio 2008 源代码管理 [英] Visual Studio 2008 source control for small teams

查看:36
本文介绍了适用于小型团队的 Visual Studio 2008 源代码管理的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在一个小型 Web 团队工作,我是目前唯一一位使用 Visual Studio 2008 Professional 构建和维护一些 Web 应用程序的 .NET 开发人员.我即将开始培训我们团队的另一名成员,因此我们为他购买了 Visual Studio 2008 Professional 的副本.我已经研究了 Visual Source Safe,但我很怀疑.我不喜欢那是基于文件系统的.理想情况下,该系统将与 SQL Server 2005 配合使用并插入 Visual Studio.由于我所在组织的 IT 环境,基于 Windows 的解决方案是最好的.

I work on a small web team where I am the only .NET developer currently using Visual Studio 2008 Professional to build and maintain a few web applications. I am about to start training another member of our team so we purchased him a copy of Visual Studio 2008 Professional. I've looked into Visual Source Safe, but I'm dubious. I don't like that is file system based. Ideally, the system would work with SQL Server 2005 and plug into Visual Studio. Windows based solutions are the best because of the IT environment of the organization I work for.

源代码控制系统有哪些选择?

What are my options for a source control system?

(如果答案存在于另一个线程中,请原谅我.)

(Forgive me if the answer exists in another thread.)

推荐答案

Subversion 与 Visual Studio 有很好的集成2008 通过 VisualSVN十字章.

Subversion has good integration with Visual Studio 2008 through VisualSVN and Ankh.

SourceSafe 很危险.你说得对,基于文件共享的 SCM 是一个坏主意,微软自己已经淡化了它,并用 Visual Studio 团队版附带的新 SCM 取而代之.

SourceSafe is dangerous. You're right that a filesharing-based SCM is a bad idea, and Microsoft themselves have downplayed it and replaced it with a new SCM that comes with the Team edition of Visual Studio.

这篇关于适用于小型团队的 Visual Studio 2008 源代码管理的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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