Git/SVN 用于 asp.net 开发而不是 VSS？
在工作中，我们使用ASP.net 2.0和VSS。 VSS 是一个野兽，我们不断地遇到人们检查文件的问题，而且没有分支 - 让它变得疯狂。我知道 SVN/GIT 主要由开源开发人员使用，那么 ASP.NET 开发人员使用它有什么缺点吗？我一直在内部推动 SVN，但我认为 GIT 也可能是一个不错的选择。我们的团队遍布三大洲。
At work, we are using ASP.net 2.0 and VSS. VSS is a beast, we are continually having issues with people checking out files and there is no branching - makes it crazy. I know SVN/GIT is mainly used by open source developers, are there any downsides to ASP.NET developers using it? I have been pushing for SVN internally, but am thinking GIT might also be a great option. Our team is spread across 3 continents.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
我以前曾在公司环境中使用过 Subversion，并取得了巨大成功。我个人没有在企业环境中使用过 Git，但对于分布式办公室来说，它听起来很合适。
当每个人都加快速度时，预计会有一个大的“驼峰”，但放弃 VSS 绝对是一个好主意。当我们从 VSS 迁移到 SVN 时，我们从未回头。我鼓励您不要吝惜新系统的培训。让一些聪明的人阅读您选择的任何系统的文档 - 并且彻底阅读。然后弄清楚你将如何使用它，并适当地进行沟通。建议其他人确实需要使用文档中的哪些部分，并给他们足够的时间来阅读。源代码控制不应该在“按回车键并希望”的基础上完成:)
I've used Subversion in a corporate setting before with great success. I haven't personally used Git in a corporate environment, but with distributed offices it sounds like a good fit.
Expect a big "hump" while everyone gets up to speed, but moving off VSS is definitely a good idea. We never looked back when we moved from VSS to SVN. I would encourage you not to skimp on training up on the new system. Get a few smart folk to read the documentation for whichever system you pick - and read it thoroughly. Then work out how you're going to use that, and communicate that appropriately. Suggest which bits of the documentation everyone else really needs to use, and give them enough time to read it. Source control shouldn't be done on a "press return and hope" basis :)
我们是一家 100% MS 开发公司（C#、ASP.Net、SQL Server、IIS、Visual Studio、Office 等），我们不会用 20 英尺的杆子接触 VSS。 SVN 很棒。还可以获取免费的 Ankh 插件。
We're a 100% MS development house (C#, ASP.Net, SQL Server, IIS, Visual Studio, Office, etc), and we wouldn't touch VSS with a 20 foot pole. SVN is great. Get the free Ankh add-in as well.
我们正在将 SVN 用于几个 ASP.NET 项目，并且运行良好。
我们最初使用 AnkhSVN 作为 VS 插件，它基本上对我来说效果很好，但是这在全公司范围内造成了一些问题。我们现在改用 VisualSVN ，它似乎更可靠。
We are using SVN for a couple of ASP.NET projects, and it is working fine.
We have initially been working with AnkhSVN as the VS plugin, and it basically worked well for me, but company-wide it has caused some problems. We have now switched to use VisualSVN which seems to be more reliable.
SVN和GIT我都用过。两者都远远优于 VSS。如果您当前正在使用 VSS，SVN 将需要深入了解您的软件。 GIT 需要更多的理解。
SVN可以由少数熟练用户操作，非熟练用户只需学会更新和提交。 GIT 将要求每个人都了解分支、合并、搁置等。
I have used both SVN and GIT. Both are far superior to VSS. If you are currently using VSS, SVN will require getting to intimately know your software. GIT will require even more understanding.
SVN can be operated by a few proficient users and non-proficient users just learn to update and commit. GIT will require everyone to understand branching, merging, shelving, and more.
得益于 Git 扩展，我们一直在使用 Git 进行 ASP.NET 开发，并且只有两个问题——Git 的学习曲线，以及处理项目之间复杂的依赖关系。否则，这绝对是一种乐趣。 Git Extensions 提供了 Git CLI 实用程序、Windows GUI 和 Visual Studio 集成，我们可以互换使用这三者。
Git 的许多复杂性来自于它惊人的灵活性，而图形界面并不能真正掩盖这一点。 IMO，即使您不需要存储库管理员，您也需要团队中至少有一个人对学习 Git 的概念有足够的兴趣，以便他们可以帮助其他人使用更高级的功能或在出现神秘消息时帮助其他人。
我们的依赖管理问题实际上源自 .NET，而不是 Git。我们的应用程序共享一组相互依赖的通用自定义程序集，并且我们当前正在使用嵌套子模块。 Git 工作正常，但需要努力保持各部分同步。如果我们规模更大，我肯定会在这里实现一个构建系统。
如果您有一个大型团队或代码库，那么您需要考虑集成问题，以便可以顺利地将事物整合在一起。 Git 使您能够随意创建存储库并将其链接在一起的方式非常有用，美妙的分支和合并也是如此，但这些功能使得系统化代码管理和构建过程变得更加重要。
我们之前将 Subversion 与 TortoiseSVN 和 AnkhSVN 一起使用，我不推荐它。我在 *NIX 上愉快地使用了 Subversion，但在 Visual Studio 上却很痛苦。在 VS 中重命名项目经常会搞砸事情，而且每次修复都非常耗时。此外，Git 做得更快更好。
We've been using Git for ASP.NET development, thanks to Git Extensions, and have only two issues - the learning curve with Git, and handling complex dependencies between projects. Otherwise, it's been an absolute pleasure. Git Extensions provides the Git CLI utility, a Windows GUI, and Visual Studio integration, and we use all three interchangeably.
A lot of the complexity of Git comes from the fact that it is amazingly flexible, and the graphical interfaces can't really mask that. IMO, even though you don't need a repository admin you will need at least one person on the team who is interested enough to learn the concepts of Git, so that they can help others with more advanced features or when cryptic messages appear.
Our dependency management issues really arise from .NET, rather than Git. Our applications share a set of common custom assemblies which are interdependent on each other, and we are currently using nested submodules. Git works correctly, but it requires an effort to keep the pieces in sync. If we were larger I would definitely implement a build system here.
If you have a large team or code base then you need to think about the issue of integration so that you can smoothly pull things together. The way that Git enables you to create and link together repositories at will is incredibly useful, as is the wonderful branching and merging, but these features make it even more important to be systematic about your code management and build process.
We used Subversion with TortoiseSVN and AnkhSVN previously, and I would not recommend it. I used Subversion happily on *NIX, but it was grief with Visual Studio. Renaming items in VS screwed things up fairly frequently, and each time it was time consuming to fix. In addition, Git just does everything faster and better.
Git 是我用过的最好的版本控制工具，而且我用过的很多工具都比 VSS 更好。所以是的，我想说切换，切换到 Git。
Git is the best version control tool I've ever used, and many that I've used have been better than VSS. So yes, I'd say switch, and switch to Git.
我认为 TFS 是最佳选择。 Tortoise svn 还不够好，而且我认为甚至不存在一个像样的 Visual Studio Git 插件。
我还没有尝试过商业 svn 与插件，它们可能值得研究。
但 TFS 中的集成和所有其他功能使其与 Visual Studio 完美结合。
I think TFS is the way to go. Tortoise svn isn't good enough, and i don't think there even exists a decent visual studio add-in for Git.
I haven't tried the commercial svn vs-add-ins they might be worth looking into.
But the integration and every other feature in TFS makes it excellent with visual studio.
我的建议是：
1) 使用 Git，它使创建和合并分支变得非常容易
2) 如果你不能使用 Git，使用除 SourceSafe 之外的任何内容
My recommendations are:
1) Use Git, it makes really easy to create and merge branches
2) If you can't use Git, Use Anything But SourceSafe
我也在SVN上。我使用 Tortoise，但有 VStud 插件 也是如此。
I'm on SVN as well. I use Tortoise, but there are VStud add-ins as well.
SVN，毫无疑问。
VSS 很糟糕。它充其量只是一个功能性的“版本控制系统”，但它没有任何并发性。
SVN, no question about it.
VSS is horrible. It is at best a functional "revision control system", but there is nothing concurrent about it.