多个开发人员，单一解决方 [英] Multiple developers, single solution

问题描述

我公司即将开始研究ASP.NET应用程序。

将成为这个项目的两个主要开发人员。这将是一个相当深的项目（很多代码行），但不是一个非常广泛的项目

（几乎只限于几个目的，没有多少分割方法）它已经完成了很多ASP.NET开发，所以编写

应用程序不应该是一个问题，但我的问题是这个：


多个开发人员如何同时处理同一个解决方案？或者他们可以吗？

您是否需要将其拆分（数据层，表示层或类似

）？或者，如果两个人一次打开

解决方案，VS.NET会做一些好检查吗？


我基本上只是想看看什么是可能的这种情况和

其他人在他们公司做的事情。


提前完成！


Tim

My company is about to begin working on an ASP.NET application. There are
going to be two primary developers working on this project. It will be a
fairly deep project (lots of lines of code) but not a very wide project
(pretty much limited to a few purposes, not many ways to split it up).
I''ve done alot of ASP.NET development before by myself so writing the
application shouldn''t be an issue, but my question is this:

How do multiple developers work on the same solution at once? Or can they?
Do you have to split it up (data layer, presentation layer or something like
that)? Or does VS.NET do some sort of good checking if both people have the
solution open at once?

I basically just wanted to see whats possible for this type of scenario and
what others are doing in their companies.

Thans in advance!

Tim

推荐答案

你想使用版本控制工具 - VSS，CVS等。

这个工具会保留一份副本在一个公共场所的代码。

它还将为您的开发人员提供一种机制来分享代码 - 开发人员检查文件以及何时

他们完成了他们检查。当他们添加新文件，

他们让源控制工具知道文件。


否则，当一个开发人员更改了一个文件并且另一个开发人员更改了另一个文件
你将不得不以某种方式弄清楚自己如何整合两个集合

代码！


VSS或CVS以及可能的任何其他版本控制

工具将跟踪文件的更改。您可以将
设置为您的版本控制工具，只允许一个人

一次签出一个文件，或者您可以允许多个

结账，但该工具会警告开发人员，如果他尝试用
来覆盖别人的更改（合并工具）。


Jon Paugh

You want to use a version control tool - VSS, CVS, etc.
This tool will keep a copy of the code in a common place.
It will also provide a mechanism for your developers to
share the code - developers checkout the files and when
they are done they check it in. When they add new files,
they let the source control tool know about the files.

Otherwise, when one developer changes one file and
another developer changes another file, you will have to
somehow figure out yourself how to integrate the two sets
of code!

Both VSS or CVS and probably any other version control
tool will keep track of changes to files. You can either
setup your version control tool to only allow one person
to checkout a file at a time, or you can allow multiple
checkouts, but the tool will warn a developer if he tries
to overwrite someone elses changes (merge tool).

Jon Paugh

我们有计划使用的VSS。

我想我的问题更多的是

汇编。


我最初来自一个ASP世界，每个人都可以编辑文件

并替换它们并进行更改和测试，并且（例外）

of global.asa和类似的东西）你改变了什么可能不会
影响另一个与你工作在同一个项目上的用户，因为它不是

编译成一个通用的DLL文件，每个.asp页面都单独运行。


但是现在，如果我们同时打开解决方案，使更改，我们

无法在我们需要的时候进行编译，因为其他开发人员将会不时地注入错误，我也会这样做。如果我在晚上因为我的代码中的错误而无法编译，并且他保持

工作，那么他要么必须修复我的错误或让他们没有发生（通过

评论出来的东西）或类似的东西，然后才能测试他的变化。


这能更好地解释我的目标吗？


我们是一家规模很小的公司，之前我们一直在开发应用程序

主要是由一个开发人员开发的，除了一些开发人员用一个编写的DLL中的组件和另一个编写的实际应用程序。

是后者的方法我应该考虑一下这种情况吗？


感谢您的评论，


Tim


Jon Paugh <一个******* @ discussions.microsoft.com>在留言中写道

news：12 ***************************** @ phx.gbl ...

We''ve got VSS that we plan to use.
I guess more of my question was something along the lines of the
compilation.

I come from an ASP world originally, where everyone could be editing files
and replacing them and making changes and testing, and (with the exception
of global.asa and things like that) what you changed probably wouldn''t
affect another user working on the same project as you, because it wasn''t
compiled into a common DLL file, each .asp page was run separately.

But now, if we both open the solution at the same time, and make changes, we
can''t both be compiling whenever we need to because the other developer will
likely be injecting errors from time to time, as will i. And if i leave for
the night with errors in my code that keep it from compiling, and he kept
working on it, he''d either have to fix my errors or make them not happen (by
commenting things out) or something along those lines before he could test
his changes.

Does that explain better what i was getting at?

We''re a fairly small company and before now we''ve been working on apps
developed primarily by a single developer, with the exception of a few that
had components in DLLs written by one and the actual app written by another.
Is the latter approach something i should look into for this situation?

Thanks for your comments,

Tim

"Jon Paugh" <an*******@discussions.microsoft.com> wrote in message
news:12*****************************@phx.gbl...

您想使用版本控制工具 - VSS，CVS等。
此工具将代码的副本保存在一个公共位置。
它还将提供您的开发人员共享代码的机制 - 开发人员检查文件，当他们完成后，他们会检查它。当他们添加新文件时，他们让源控制工具知道文件。

否则，当一个开发人员更改一个文件并且另一个开发人员更改另一个文件时，您将不得不以某种方式弄清楚如何整合这两个文件
代码！

VSS或CVS以及可能的任何其他版本控制工具都会跟踪文件的变化。你可以设置你的版本控制工具，只允许一个人一次签出一个文件，或者你可以允许多个
签出，但是如果他尝试，该工具会警告开发人员
覆盖别人的变化（合并工具）。

Jon Paugh

You want to use a version control tool - VSS, CVS, etc.
This tool will keep a copy of the code in a common place.
It will also provide a mechanism for your developers to
share the code - developers checkout the files and when
they are done they check it in. When they add new files,
they let the source control tool know about the files.

Otherwise, when one developer changes one file and
another developer changes another file, you will have to
somehow figure out yourself how to integrate the two sets
of code!

Both VSS or CVS and probably any other version control
tool will keep track of changes to files. You can either
setup your version control tool to only allow one person
to checkout a file at a time, or you can allow multiple
checkouts, but the tool will warn a developer if he tries
to overwrite someone elses changes (merge tool).

Jon Paugh

Seee
http：/ /msdn.microsoft.com/library/de...l/tdlg_ch2.asp

和隔离模式。


大图是每个开发人员获得他可以在localhost上运行的项目的副本

。他可以随意签出文件进行编辑，并在本地测试更改

，避免全局问题。当更改正常时，它们将被存储回中央位置的
。


每个开发人员都可以通过获取最新版本来随意刷新。它只需要一点点学习就可以很好地为我们工作（避免在不能编译的情况下检查

）。


Patrice

-


Tim Mulholland <钛*********** @ nospamaddress.com> écritdansle message

de news：Oz ************** @ TK2MSFTNGP12.phx.gbl ...

Seee
http://msdn.microsoft.com/library/de...l/tdlg_ch2.asp
and the isolated mode.

The big picture is that each developer gets a copy of the project he can run
on localhost. He can checkout files to edit them at will and test changes
locally avoiding global problems. When changes are ok they are stored back
at the central location.

Each developer can get a refresh at will by getting the last version. It
works pretty well for us with just a little disscipline (avoiding checking
in changes that won''t compile).

Patrice
--

"Tim Mulholland" <Ti***********@nospamaddress.com> a écrit dans le message
de news:Oz**************@TK2MSFTNGP12.phx.gbl...

我们'我们计划使用VSS。
我想我的问题更多的是
编译的内容。

我原来来自ASP世界，其中每个人都可以编辑文件
并替换它们并进行更改和测试，（除了global.asa和类似的东西之外）你改变的内容可能不会影响另一个用户在同一个项目上工作，因为它没有被编译成一个通用的DLL文件，每个.asp页面都是单独运行的。

但是现在，如果我们都打开了同时解决方案，并进行更改，
我们无法在需要时编译，因为其他开发人员
可能会不时地注入错误，我也是如此。如果我在晚上留下
而我的代码中存在错误以防止编译，并且他继续工作，他要么必须修复我的错误或者让它们不发生$ b在他可以测试他的变化之前，$ b（通过评论出来的东西）或类似的东西。

这能更好地解释我的目标吗？

我们是一家规模很小的公司，在此之前我们一直致力于开发主要由单个开发人员开发的应用程序，除了少量
，其中包含由一个人编写的DLL中的组件由
另外写的实际应用程序。后一种方法是否应该针对这种情况进行研究？

感谢您的评论，

Tim

  Jon Paugh" <一个******* @ discussions.microsoft.com>在消息中写道
新闻：12 ***************************** @ phx.gbl ...

We''ve got VSS that we plan to use.
I guess more of my question was something along the lines of the
compilation.

I come from an ASP world originally, where everyone could be editing files
and replacing them and making changes and testing, and (with the exception
of global.asa and things like that) what you changed probably wouldn''t
affect another user working on the same project as you, because it wasn''t
compiled into a common DLL file, each .asp page was run separately.

But now, if we both open the solution at the same time, and make changes, we can''t both be compiling whenever we need to because the other developer will likely be injecting errors from time to time, as will i. And if i leave for the night with errors in my code that keep it from compiling, and he kept
working on it, he''d either have to fix my errors or make them not happen (by commenting things out) or something along those lines before he could test
his changes.

Does that explain better what i was getting at?

We''re a fairly small company and before now we''ve been working on apps
developed primarily by a single developer, with the exception of a few that had components in DLLs written by one and the actual app written by another. Is the latter approach something i should look into for this situation?

Thanks for your comments,

Tim

"Jon Paugh" <an*******@discussions.microsoft.com> wrote in message
news:12*****************************@phx.gbl...

您想使用版本控制工具 - VSS，CVS等。
此工具将代码的副本保存在一个公共位置。
它还将为您的开发人员提供一种机制分享代码 - 开发人员检查文件，当他们完成文件时，他们会检查它们。当他们添加新文件时，他们让源代码控制工具知道这些文件。

VSS或CVS以及可能的任何其他版本控制工具都会跟踪文件的变化。你可以设置你的版本控制工具，只允许一个人一次签出一个文件，或者你可以允许多个
签出，但是如果他尝试，该工具会警告开发人员
覆盖别人的变化（合并工具）。

Jon Paugh

You want to use a version control tool - VSS, CVS, etc.
This tool will keep a copy of the code in a common place.
It will also provide a mechanism for your developers to
share the code - developers checkout the files and when
they are done they check it in. When they add new files,
they let the source control tool know about the files.

Otherwise, when one developer changes one file and
another developer changes another file, you will have to
somehow figure out yourself how to integrate the two sets
of code!

Both VSS or CVS and probably any other version control
tool will keep track of changes to files. You can either
setup your version control tool to only allow one person
to checkout a file at a time, or you can allow multiple
checkouts, but the tool will warn a developer if he tries
to overwrite someone elses changes (merge tool).

Jon Paugh

这篇关于多个开发人员，单一解决方的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！