组织依赖项目的最佳方法？ [英] Best way to organize dependant projects?

问题描述

我有一组依赖于其他项目的项目（可以说是实用程序），问题是每次我更改这些实用程序中任何一个的代码时，我的同事都需要采用最新的代码并在其计算机上构建以使用最新的程序集。
有没有好的标准解决方案？还是只是将dll集中在共享文件夹上？

PS：

我们正在使用MS Source Safe 2005和我不希望我的同事每次都拿源代码并在他们的机器上构建，因为他们只需要二进制文件而不是代码。

解决方案

如果您将Subversion用作源代码管理系统，则可以使用 SVN外部组件为此。
这样，当他们对there文件夹进行根更新时，它们将自动拉出实用程序的新版本。您还可以以只读方式为他们提供源代码控制，以便他们可以查看实用程序代码，但他们无权提交更改。

我们在工作中使用它，效果很好。但是请注意，有时候您不想每次都进行更新，因为使用新版本可能会破坏某些功能。这是贵公司必须处理的事情。我们为实用程序的市长版本提供了SVN分支（或标签），因此，如果更改市长版本，我们将创建一个新版本，然后，人们将需要手动更改其SVN外部以指向他们的新版本。 / p>

I have a set of projects that depend on other projects (you can say utilities), the problem is every time I change the code of any one of these utilities my colleagues need to take the latest code and build on their machines to use the latest assemblies. Is there a good standard solution? or simply centralized the dlls on a shared folder?

P.S:

We are using MS source safe 2005 and I do not want my colleagues to take the source code everytime and build on their machines as they only need the binaries not the code.

解决方案

If you use Subversion as a Source Control system, you can use SVN Externals to do this. That way they will automaticly pull the new versions of your utilities, when they do a root update of there folder. You can also give them the Source Control, in a read only way, so they can look at the utility code, but they dont have the right to commit changes.

We use this at work, and it works perfectly. But be aware, that sometimes you don't want to update your utilities every time you do an update, as you may be breaking something by using the new version. This is something that your company must have a way to handle. We have SVN Branches (or tags) for mayor versions of the utilities, so if we change something mayor, we make a new version, and people will then have to manually change their SVN External to point to the new version if they wish.

这篇关于组织依赖项目的最佳方法？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！