Visual Studio 2008的小球队的源代码控制 [英] Visual Studio 2008 source control for small teams

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

问题描述

我工作在一个小的网络团队里我目前使用Visual Studio 2008专业版,以建立和维持一些Web应用程序的唯一.NET开发人员。我将要开始训练我们团队的其他成员,所以我们为他买的Visual Studio 2008专业版的副本。我看着Visual源安全,但我怀疑。我不喜欢的基础就是文件系统。理想情况下,该系统将与SQL Server 2005和插入到Visual Studio中。基于Windows系统解决方案是因为我工作的组织的IT环境的最好的。

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

推荐答案

颠覆通过与Visual Studio 2008的良好集成的的VisualSVN 安赫

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

SourceSafe是危险的。你说的没错,一个文件共享为基础的供应链管理是一个坏主意,和微软自己低估了它,用附带的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天全站免登陆