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.
我在一个小型团队工作,我是目前唯一使用Visual Studio 2008 Professional构建和维护一些Web应用程序的.NET开发人员。我即将开始培训我们团队的另一名成员,因此我们向他购买了一份Visual Studio 2008 Professional。我看过Visual Source Safe,但我很怀疑。我不喜欢那是基于文件系统的。理想情况下,系统可以与SQL Server 2005一起使用并插入Visual Studio。基于Windows的解决方案是最好的,因为我所在的组织的IT环境。
What are my options for a source control system?
我对源控制系统有哪些选择?
(Forgive me if the answer exists in another thread.)
(如果答案存在于另一个帖子中,请原谅我。)
12 个解决方案
#1
27
Subversion has good integration with Visual Studio 2008 through VisualSVN and Ankh.
Subversion通过VisualSVN和Ankh与Visual Studio 2008很好地集成。
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.
SourceSafe很危险。你是对的,基于文件共享的SCM是一个坏主意,微软自己已经淡化了它,并用Visual Studio团队版附带的新SCM取而代之。
#2
11
I can't believe nobody has mentioned SourceGear Vault. It stores your code in SQL Server, integrates extremely well into VS, and is an excellent replacement/alternative to Source Safe. Since their single-user license is free, I even use it when coding at home. Plus, it's the company founded/run by Eric Sink.
我不敢相信没有人提到过SourceGear Vault。它将您的代码存储在SQL Server中,非常好地集成到VS中,是Source Safe的绝佳替代/替代。由于他们的单用户许可是免费的,我甚至在家里编码时使用它。此外,它是由Eric Sink创立/运营的公司。
#3
5
Has any body given Git any thought? There is a very usable solution for windows called GitExtensions here. It integrates with Visual Studio Professional trough an extra menu and optional toolbar. Unlike Subversion, Git is distributed, which means you can commit locally to your copy of the repository, and afterwards push the changes to the server. The bottom line? Git is FAST! It's storage is also more efficient than subversion, which means your repository takes up less space.
有没有机构给Git任何想法?这里有一个非常有用的Windows解决方案,叫做GitExtensions。它通过一个额外的菜单和可选的工具栏与Visual Studio Professional集成。与Subversion不同,Git是分布式的,这意味着您可以在本地提交您的存储库副本,然后将更改推送到服务器。底线? Git很快!它的存储也比subversion更高效,这意味着您的存储库占用的空间更少。
#4
3
Subversion. Free. Visual SVN is a great add on, and is fairly inexpensive.
颠覆。*。 Visual SVN是一个很好的补充,并且相当便宜。
#5
3
Definitely, as most people says, Subversion + VisualSVN.
绝对是,正如大多数人所说,Subversion + VisualSVN。
VisualSVN is a fairly cheap addon at $49, subversion is free and very stable. We use that for teams of 10-15 people and it works really well for us. The only con is that it is file-system based.
VisualSVN是一个相当便宜的插件,价格为49美元,颠覆是免费且非常稳定的。我们将其用于10-15人的团队,对我们来说效果非常好。唯一的缺点是它是基于文件系统的。
On the other hand, if you have a very specific need for it not to be on the file system i would NOT recommend Visual Source Safe, on my last job we had a lot of trouble with it and lost precious days of work. If you want to go that way get something like sourcegear vault which is database based. There is also Team Foundation Server from Microsoft but I believe it is really expensive (and heavy) for small teams.
另一方面,如果你有一个非常特殊的需要,它不在文件系统上我不会推荐Visual Source Safe,在我上一份工作中我们遇到了很多麻烦并且失去了宝贵的工作日。如果你想以这种方式获得类似于基于数据库的sourcegear vault。还有来自微软的Team Foundation Server,但我认为这对小型团队来说真的很贵(而且很重)。
#6
2
Visual SVN might work for you, it is supposed to integrate well and is relatively cheap at ~$50 per license. I've been considering buying it myself, so far I just use Tortoise SVN as I do relatively little non-Eclipse work right now.
Visual SVN可能对您有用,它应该很好地集成并且相对便宜,每个许可证约50美元。我一直在考虑自己购买它,到目前为止我只使用Tortoise SVN,因为我现在做的工作相对较少。
#7
2
Team Foundation Server does satisfy your requirements of working with SQL Server, but is probably overkill for such a small development team.
Team Foundation Server确实满足您使用SQL Server的要求,但对于这样一个小型开发团队来说可能有点过分。
I would recommend using Subversion (free) for source control along with VisualSVN ($49) for the visual studio integration. There is also an excellent Subversion client for windows explorer called TortoiseSVN, which is awesome.
我建议使用Subversion(免费)进行源代码控制以及VisualSVN(49美元)用于visual studio集成。还有一个优秀的Windows浏览器Subversion客户端名为TortoiseSVN,非常棒。
The nice thing about giving something like Subversion a try is that it is free and very easy to set up. It will also scale up to a pretty large team. It is worth a shot before investing effort in MSFTs Team Foundation Server.
尝试使用Subversion这样的东西是一件好事,它是免费且易于设置的。它还将扩展到一个非常大的团队。在投资MSFT Team Foundation Server之前,值得一试。
#8
1
Microsoft's Team Foundation Server integrates fully into VS2008 and uses SQL Server for its back end. The downside is that it's a very expensive solution.
Microsoft的Team Foundation Server完全集成到VS2008中,并使用SQL Server作为后端。缺点是它是一个非常昂贵的解决方案。
#9
1
Why not use a SVN server? That way, all your developers can use it, and there is a very good free Windows Client for it (TortoiseSVN). You can integrate SVN support with TortoiseSVN into Visual Studio with VisualSVN, which is commercial, but not actually expensive.
为什么不使用SVN服务器?这样,所有开发人员都可以使用它,并且有一个非常好的免费Windows客户端(TortoiseSVN)。您可以使用VisualSVN将SVN支持与TortoiseSVN集成到Visual Studio中,VisualSVN是商业的,但实际上并不昂贵。
#10
1
We switched over from SourceSafe to tfs recently and have found it to work quite capably.
我们最近从SourceSafe切换到了tfs,并发现它非常有效。
The only notable exception in features we exercised is file linking.
我们运用的功能中唯一值得注意的例外是文件链接。
To keep the costs down, we make sure that we get the Gold Certified Partner status.
为了降低成本,我们确保获得金牌认证合作伙伴资格。
#11
1
I recommend subversion, coupled with AnkhSVN, a plugin (Free!) that integrates Subversion with the Visual Studio IDE.
我推荐subversion,加上AnkhSVN,一个将Subversion与Visual Studio IDE集成的插件(Free!)。
If you use the svnserve distribution that's free from CollabNet (Windows binaries: here), setup is very simple. Administration is very easy. And the product works very well.
如果您使用免费的CollabNet(Windows二进制文件:此处)的svnserve发行版,则设置非常简单。管理很容易。产品运作良好。
It is still file-system based, but that isn't really a problem. Make sure that you back-up regularly, both full dumps and hot-copies (both of which are explained in detail in the documentation).
它仍然是基于文件系统的,但这不是一个真正的问题。确保定期备份,包括完整转储和热备份(两者都在文档中详细说明)。
#12
1
Visual Source Safe has a bad rap from it's earlier incarnations. They came out with a new version in 2005, and it solves many of the problems of earlier versions. I don't think they've solved the branching problems though. They have a client/server portion now (well, it's http based) so that solves some of the remote issues.
Visual Source Safe从它的早期版本中得到了糟糕的说唱。他们在2005年推出了新版本,它解决了早期版本的许多问题。我不认为他们已经解决了分支问题。他们现在有一个客户端/服务器部分(好吧,它基于http),以便解决一些远程问题。
SVN is probably a better solution, but VSS isn't as bad as it once was.
SVN可能是一个更好的解决方案,但VSS并不像以前那么糟糕。
#1
27
Subversion has good integration with Visual Studio 2008 through VisualSVN and Ankh.
Subversion通过VisualSVN和Ankh与Visual Studio 2008很好地集成。
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.
SourceSafe很危险。你是对的,基于文件共享的SCM是一个坏主意,微软自己已经淡化了它,并用Visual Studio团队版附带的新SCM取而代之。
#2
11
I can't believe nobody has mentioned SourceGear Vault. It stores your code in SQL Server, integrates extremely well into VS, and is an excellent replacement/alternative to Source Safe. Since their single-user license is free, I even use it when coding at home. Plus, it's the company founded/run by Eric Sink.
我不敢相信没有人提到过SourceGear Vault。它将您的代码存储在SQL Server中,非常好地集成到VS中,是Source Safe的绝佳替代/替代。由于他们的单用户许可是免费的,我甚至在家里编码时使用它。此外,它是由Eric Sink创立/运营的公司。
#3
5
Has any body given Git any thought? There is a very usable solution for windows called GitExtensions here. It integrates with Visual Studio Professional trough an extra menu and optional toolbar. Unlike Subversion, Git is distributed, which means you can commit locally to your copy of the repository, and afterwards push the changes to the server. The bottom line? Git is FAST! It's storage is also more efficient than subversion, which means your repository takes up less space.
有没有机构给Git任何想法?这里有一个非常有用的Windows解决方案,叫做GitExtensions。它通过一个额外的菜单和可选的工具栏与Visual Studio Professional集成。与Subversion不同,Git是分布式的,这意味着您可以在本地提交您的存储库副本,然后将更改推送到服务器。底线? Git很快!它的存储也比subversion更高效,这意味着您的存储库占用的空间更少。
#4
3
Subversion. Free. Visual SVN is a great add on, and is fairly inexpensive.
颠覆。*。 Visual SVN是一个很好的补充,并且相当便宜。
#5
3
Definitely, as most people says, Subversion + VisualSVN.
绝对是,正如大多数人所说,Subversion + VisualSVN。
VisualSVN is a fairly cheap addon at $49, subversion is free and very stable. We use that for teams of 10-15 people and it works really well for us. The only con is that it is file-system based.
VisualSVN是一个相当便宜的插件,价格为49美元,颠覆是免费且非常稳定的。我们将其用于10-15人的团队,对我们来说效果非常好。唯一的缺点是它是基于文件系统的。
On the other hand, if you have a very specific need for it not to be on the file system i would NOT recommend Visual Source Safe, on my last job we had a lot of trouble with it and lost precious days of work. If you want to go that way get something like sourcegear vault which is database based. There is also Team Foundation Server from Microsoft but I believe it is really expensive (and heavy) for small teams.
另一方面,如果你有一个非常特殊的需要,它不在文件系统上我不会推荐Visual Source Safe,在我上一份工作中我们遇到了很多麻烦并且失去了宝贵的工作日。如果你想以这种方式获得类似于基于数据库的sourcegear vault。还有来自微软的Team Foundation Server,但我认为这对小型团队来说真的很贵(而且很重)。
#6
2
Visual SVN might work for you, it is supposed to integrate well and is relatively cheap at ~$50 per license. I've been considering buying it myself, so far I just use Tortoise SVN as I do relatively little non-Eclipse work right now.
Visual SVN可能对您有用,它应该很好地集成并且相对便宜,每个许可证约50美元。我一直在考虑自己购买它,到目前为止我只使用Tortoise SVN,因为我现在做的工作相对较少。
#7
2
Team Foundation Server does satisfy your requirements of working with SQL Server, but is probably overkill for such a small development team.
Team Foundation Server确实满足您使用SQL Server的要求,但对于这样一个小型开发团队来说可能有点过分。
I would recommend using Subversion (free) for source control along with VisualSVN ($49) for the visual studio integration. There is also an excellent Subversion client for windows explorer called TortoiseSVN, which is awesome.
我建议使用Subversion(免费)进行源代码控制以及VisualSVN(49美元)用于visual studio集成。还有一个优秀的Windows浏览器Subversion客户端名为TortoiseSVN,非常棒。
The nice thing about giving something like Subversion a try is that it is free and very easy to set up. It will also scale up to a pretty large team. It is worth a shot before investing effort in MSFTs Team Foundation Server.
尝试使用Subversion这样的东西是一件好事,它是免费且易于设置的。它还将扩展到一个非常大的团队。在投资MSFT Team Foundation Server之前,值得一试。
#8
1
Microsoft's Team Foundation Server integrates fully into VS2008 and uses SQL Server for its back end. The downside is that it's a very expensive solution.
Microsoft的Team Foundation Server完全集成到VS2008中,并使用SQL Server作为后端。缺点是它是一个非常昂贵的解决方案。
#9
1
Why not use a SVN server? That way, all your developers can use it, and there is a very good free Windows Client for it (TortoiseSVN). You can integrate SVN support with TortoiseSVN into Visual Studio with VisualSVN, which is commercial, but not actually expensive.
为什么不使用SVN服务器?这样,所有开发人员都可以使用它,并且有一个非常好的免费Windows客户端(TortoiseSVN)。您可以使用VisualSVN将SVN支持与TortoiseSVN集成到Visual Studio中,VisualSVN是商业的,但实际上并不昂贵。
#10
1
We switched over from SourceSafe to tfs recently and have found it to work quite capably.
我们最近从SourceSafe切换到了tfs,并发现它非常有效。
The only notable exception in features we exercised is file linking.
我们运用的功能中唯一值得注意的例外是文件链接。
To keep the costs down, we make sure that we get the Gold Certified Partner status.
为了降低成本,我们确保获得金牌认证合作伙伴资格。
#11
1
I recommend subversion, coupled with AnkhSVN, a plugin (Free!) that integrates Subversion with the Visual Studio IDE.
我推荐subversion,加上AnkhSVN,一个将Subversion与Visual Studio IDE集成的插件(Free!)。
If you use the svnserve distribution that's free from CollabNet (Windows binaries: here), setup is very simple. Administration is very easy. And the product works very well.
如果您使用免费的CollabNet(Windows二进制文件:此处)的svnserve发行版,则设置非常简单。管理很容易。产品运作良好。
It is still file-system based, but that isn't really a problem. Make sure that you back-up regularly, both full dumps and hot-copies (both of which are explained in detail in the documentation).
它仍然是基于文件系统的,但这不是一个真正的问题。确保定期备份,包括完整转储和热备份(两者都在文档中详细说明)。
#12
1
Visual Source Safe has a bad rap from it's earlier incarnations. They came out with a new version in 2005, and it solves many of the problems of earlier versions. I don't think they've solved the branching problems though. They have a client/server portion now (well, it's http based) so that solves some of the remote issues.
Visual Source Safe从它的早期版本中得到了糟糕的说唱。他们在2005年推出了新版本,它解决了早期版本的许多问题。我不认为他们已经解决了分支问题。他们现在有一个客户端/服务器部分(好吧,它基于http),以便解决一些远程问题。
SVN is probably a better solution, but VSS isn't as bad as it once was.
SVN可能是一个更好的解决方案,但VSS并不像以前那么糟糕。