visual-studio CVS 和 Visual Studio 2008 - 集成选项
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/104579/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
CVS and Visual Studio 2008 - integration options
提问by DK.
I'd like to increase developers' "comfort level" in our team a bit. We are using Visual Studio 2008 and TortoiseCVS + WinCVS, but no integration as of yet.
我想提高我们团队中开发人员的“舒适度”。我们正在使用 Visual Studio 2008 和 TortoiseCVS + WinCVS，但目前还没有集成。
In your CVS/Visual Studio experience, what is the best integration tool in terms of "supports basic CVS functionality add/diff/update/commit/annotate/etc", "works out of the box", almost "bug-free"?
在您的 CVS/Visual Studio 体验中，就“支持基本 CVS 功能添加/差异/更新/提交/注释/等”、“开箱即用”、几乎“无错误”而言，最好的集成工具是什么？
- a) commercial
- b) free or open source
- a) 商业的
- b) 免费或开源
Edit:
编辑：
There are 2 commercial MSSCCI bridge solutions I've found so far: PushOk.com and TamTam (daveswebsite.com). Both were developed quite a long time ago and now have only minor updates. Being MSSCCI bridges, they are somewhat limited in functionality and can not provide all the nice features of vsPackage SCC provider, but are probably better than nothing.
到目前为止，我发现了 2 个商业 MSSCCI 桥接解决方案：PushOk.com 和 TamTam (daveswebsite.com)。两者都是很久以前开发的，现在只有很小的更新。作为 MSSCCI 桥接器，它们在功能上有所限制，无法提供 vsPackage SCC 提供程序的所有优秀功能，但可能总比没有好。
采纳答案by Chris Charabaruk
You might be stuck with one of those MSSCCI bridges you mentioned. As it is, not too many people still use CVS, especially those using Visual Studio (most of them seem to use Team System's revision control, or Subversion).
您可能会遇到您提到的那些 MSSCCI 桥接器之一。事实上，仍然没有太多人使用 CVS，尤其是那些使用 Visual Studio 的人（他们中的大多数似乎使用 Team System 的修订控制，或 Subversion）。
There's always the possibility of hacking together your own macros to take care of CVS operations, but this has the disadvantage of not giving you real, in-depth integration the way a an SCC provider, or even an old brige, would.
总是有可能将您自己的宏组合在一起来处理 CVS 操作，但这样做的缺点是无法像 SCC 提供商甚至旧桥那样为您提供真正的、深入的集成。
