OT（略）：协调多个开发人员 [英] OT (slightly): Coordinating Multiple Developers
问题描述
到目前为止，我一直在为小型团队（1-3名开发人员）工作，而且我们已经能够支持
以保持彼此的方式。现在我要开始研究一个项目
将有5个开发人员。我将非常感谢我们如何能够继续开发，而不必担心谁正在处理什么
文件。
我们正在开发SQL Server 2005，VS 2005专业版（对于每个人来说，管理层都不会花费
为$ 10,000团队版），我们将拥有< br $>
Visual SourceSafe。
当然这些工具（如果有的话，甚至团队版）也不会阻止
us从而陷入困境...因此我的询问（文章，链接，提示，
建议等）。
谢谢！
Until now I have worked on small teams (1-3 developers) and we''ve been able
to stay out of each others way. Now I''m about to start work on a project
that will have 5 developers. I would appreciate some guidance on how we can
proceed to develop without having to worry about "who is working on what
files".
We''re developing with SQL Server 2005, VS 2005 Pro (no way management is
going to spring for the $10,000 team edition for everybody), and we''ll have
Visual SourceSafe.
Of course these tools (even the Team edition if we had it) wouldn''t prevent
us from getting into trouble... thus my inquiry (for articles, links, tips,
suggestions, etc).
Thanks!
推荐答案
每个人的10,000个团队版本，我们将拥有
Visual SourceSafe。
当然这些工具（如果我们有这个工具，甚至团队版）都不会阻止我们因为陷入困境而导致...因此我的询问（文章，链接，提示，
建议等）。
谢谢！
10,000 team edition for everybody), and we''ll have
Visual SourceSafe.
Of course these tools (even the Team edition if we had it) wouldn''t prevent
us from getting into trouble... thus my inquiry (for articles, links, tips,
suggestions, etc).
Thanks!
我的建议如下：
使用良好的分层开发。这将有助于让人们远离彼此
方式。
（如果有人在mypage.aspx上工作，他们不会干扰某人
写一个新的业务逻辑规则）
有一个在一天结束时...你需要检查你的代码
可构建的格式
又名，不要检查一下，这样就无法编译。
非常肛门/严格检查.sln和/或.csproj（.vbproj）
文件。
（解决方案和项目），因为这会搞砸其他人。
这将在大多数时间保持秩序。
最大的问题是。 。
UserA创建一个新文件
MyNewClass.cs
他们编辑一个现有的类/ file（MyExistingClass.cs），并在其中编写代码
使用MyNewClass（.cs）
他们检查项目。他们添加了文件。
他们签入项目。他们签入MyNewClass.cs。
他们忘记签入MyNewClass.cs。现在其他人无法建立。
一个好的男孩政策，比如开发人员这样做了吗？b $ b为其他人购买苏打水在该组中如果他们搞砸了可以解决那个问题。
不，我不是在开玩笑。机器上的几轮苏打水由一个人忘记了，会给他/她留下一些记忆。
< a rel =nofollowhref =http://sholliday.spaces.msn.com/PersonalSpace.aspxtarget =_ blank> http://sholliday.spaces.msn.com/PersonalSpace.aspx 2006年5月24日
6/5/2006
有一个启动分层开发示例：
"史密琴斯" < A@B.COM>在消息中写道
新闻：OW ************** @ TK2MSFTNGP02.phx.gbl ...
My advice is this:
Use good tiered development. This will help keep people out of each others
way.
(if someone is workign on the mypage.aspx, they won''t interfere with someone
writing up a new business logic rule)
Have a "at the end of the day... you need to check in your code in a
buildable format"
aka, don''t check something in that makes it so you can''t compile.
Be very anal/strick about checking out the .sln and/or the .csproj (.vbproj)
files.
(Solution and Projects) because that will screw others.
This will keep things in order most of the time.
The biggest gotcha is that..
UserA creates a new file
MyNewClass.cs
They edit an existing class/file (MyExistingClass.cs), and write code in it
which uses MyNewClass (.cs)
They check out the project. They add the file.
They check in the project. They check in MyNewClass.cs.
They FORGET to check in MyNewClass.cs. Now others can''t build.
A good ole boy policy of something like "The developer who does this has to
buy sodas for everyone else in the group" if they screw up can solve that
issue.
No, Im'' not joking. A few rounds of sodas from the machine by the one
numbnutt who keeps forgetting, will burn some memory into him/her.
http://sholliday.spaces.msn.com/PersonalSpace.aspx 5/24/2006
6/5/2006
has a start up tiered development example:
"Smithers" <A@B.COM> wrote in message
news:OW**************@TK2MSFTNGP02.phx.gbl...
直到现在我已经工作了在小团队（1-3名开发人员）和我们已经
能够保持彼此的方式。现在我要开始研究一个有5个开发人员的项目。我将非常感谢有关我们如何进行开发而不必担心谁正在处理什么
文件的一些指导。
我们正在使用SQL开发Server 2005，VS 2005 Pro（对于每个人来说，管理层都不会出现
Until now I have worked on small teams (1-3 developers) and we''ve been able to stay out of each others way. Now I''m about to start work on a project
that will have 5 developers. I would appreciate some guidance on how we can proceed to develop without having to worry about "who is working on what
files".
We''re developing with SQL Server 2005, VS 2005 Pro (no way management is
going to spring for the
10,000团队版本），我们将
拥有Visual SourceSafe 。
当然这些工具（即使是我们拥有的Team版本）也不会因为我的问题而无法接受麻烦...因此我的询问（文章，链接，
提示，建议等）。
谢谢！
10,000 team edition for everybody), and we''ll have Visual SourceSafe.
Of course these tools (even the Team edition if we had it) wouldn''t prevent us from getting into trouble... thus my inquiry (for articles, links, tips, suggestions, etc).
Thanks!
这篇关于OT（略）：协调多个开发人员的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
