0

更少的问题，更多的建议和建议是“我从哪里开始 TF？”

启动环境：VS 2010 Pro, C#, VSS 2005, single developer, multple VSS repositories, limited code re-use

目前我有（大部分是继承的，直到现在还没有时间改变）多个 VSS 存储库，通常带有 C&P 的实用程序/工具类/项目。文档位于网络共享上（我将 BRD、UAT 测试脚本、用于 db 构建的 sql 脚本等都作为“文档”用于此目的）。很少或没有单元测试，也没有 CI/构建自动化。

我即将获得两个新开发者，因此我想改变环境

可能的结束环境：VS 2010 Pro, C#, Java (not sure of IDE yet), 3 developers, documentation under source control, re-used code, (automated) unit testing, CI builds, incemental revision/build numbers

我最初的想法是转向 SVN 或类似的、单一存储库、单一“主”解决方案、多个“工作”解决方案。MSTest（因为它内置在 VS2010 中？），通过 CC.Net 或 TeamCity 进行 CI。

我已经阅读了很多关于独立完成这些任务的内容，例如支持/反对每个源代码控制系统的论据，支持/反对将文档添加到源代码控制中的论据，但一次做所有事情都没有！

注意：我们仍然是一个小团队，所以允许一些手工工作，但最好是最少的，而且我们没有预算，所以需要免费或“对小团队免费”！

有人对从哪里开始有建议吗？使用什么工具？如何从 VSS 迁移出去？我应该使用“主”解决方案还是有一个 CI 工具可以为我“留下印象”？例如，查看“实用程序代码”更改是否破坏了其他任何东西的地方？

（脚注：我知道我们仍然需要编写单元测试！）

4

3 回答 3

1

小型团队（最多 5 名团队成员）的一个不错的选择是 Team Foundation Service：https ://tfs.visualstudio.com/

Team Foundation Service 是 Team Foundation Server 的云托管版本。它将为您提供运行项目所需的所有东西，例如可用于持续集成的源代码控制、工作项和自动构建。

Microsoft released a tool that will migrate your repositories to TFS: Visual Source Safe Upgrade Tool for Team Foundation Server.

I would also advice moving to Visual Studio 2012. It's a really big improvement on VS2010. Since you are a small company you probably can apply for Microsoft BizSpark. That will give you three years of free software, Azure and support. It can really help you getting started.

Regarding your Documentation question, have a look at the SSW Rules for better .NET Projects. Rule 45 mentions how you could store your documentation with your project under source control.

All the other things you mention (Sql scripts, test scripts) should also be under source control. You can add them to a specific folder beneath your solution.

Adding Unit Test to an existing project will be a hassle. Working Effectively with Legacy Code is a book that offers some great advice on how to start. If you have no experience with writing unit tests you should first study the subject or hire an external consultant. In the projects I consult on a I see that people start enthusiastically but stop using unit tests because they run into problems.

于 2012-12-17T08:04:12.347 回答
1

I was you, 2 years ago. We went with SVN + TeamCity and never looked back. SVN is fully free and TC is effectively free*. Both work beautifully with Java and .Net. You can store and integrate your code onsite with as little as one server. If I were doing it today I might consider GitHub, but for a central repo model, SVN is great.

Regarding the transition out of VSS, this is sage advice. I spent a bunch of time manually converting the old VSS repos to SVN and there was zero practical value in keeping the (lousy, spotty) history around in SVN.

*TC is free for unlimited users and up to 20 build configurations. If you hit that wall, then you'll be realizing enough business value to get $MEGACORP to pony up for the full version.

于 2012-12-18T01:22:19.880 回答
0

If you need:

  • To host your own code (not outside)
  • A free solution for up to 15 users
  • Strong branching and merging (which probably you do not need at the very beginning until you're fully unplugged from the VSS matrix ;) )
  • Ability to work distributed...
  • Excellent Visual Studio integration

Why don't you give a try to ww.plasticscm.com?

Disclaimer: I do work for the company... but still... it should be a good option for you! :) We define ourselves as the DVCS for Windows!

于 2012-12-26T11:47:07.780 回答