如何将Web项目拆分为服务器项目 [英] How to Split a Web Project to serveral Projects

查看:187
本文介绍了如何将Web项目拆分为服务器项目的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个由开发人员开发的网站.
现在,康妮聘请了其他一些开发人员,每个开发人员都对每个部分负责.顺便说一句,我不希望每个开发人员都可以访问所有项目文件并且可以独立工作,但是他们可以让其他开发人员编译文件(dll文件).
管理员可以收集DLL并将其编译为以前相同的一个项目.

例如,有一些目录,例如:
A目录
B目录
C目录
D目录

每个目录中都有一些可以调用其他目录的URL.

在此先感谢您.

I have a Web site which was developed by one developer.
Now the compony hired some other developers,each developer is responsile for each part. BTW I dont want each developer to have access to all the project files and can work independent, but they can have others complied files(dll files).
And the admin can gather the DLLs and compile them as one project the same before.

For example there are some directoies like :
A-Directory
B-Directory
C-Directory
D-Directory

in each directory there are some URLs which can call other directories.

Thanks in advance.

推荐答案

这听起来像是我的祸根:每个开发人员都将在各自的仓库中工作,一个dll的更改可能在没有警告的情况下影响另一个dll,如果开发人员不知道更改的潜在影响,则情况将变得更糟.最后,在每个新版本中,您都必须使用它们将新的dll重新分配给每个团队.很难管理.

您可以使用源代码控制来实现所需的功能.无论如何,这都是一个好主意,即使没有您的要求,因为它可以跟踪更改,大多数都可以让您在需要时回滚代码并提供其他支持,我曾经使用过Visual Studio Team System(非常好),Visual源安全(不好)和Merant版本管理器.也有开放源代码控制,但是我所知道的唯一一个使源代码公开可用.

有了源代码控制后,便可以为每个团队创建存储库,在他们签入,构建其dll并将其重新注册到其他团队存储库时.
This sounds like a recipie for disaster to me: each dev will work in their own silo, changes in one dll can impact another without warning, this will be made worse by the dev being unaware of the potential impact of their changes. Finally, at each new build you will have to re-distribute the new dlls to each team using them. It will be very hard to manage.

You can use source control to acheive what you want. It is a good idea anyway, even without your requirents as it keeps track of changes, most allow you to roll-back code if needed and provide other support as well, I''ve used Visual Studio Team System (very good), Visual Source Safe (not good) and Merant Version Manager a while back. There are also Open-Source source control, but the only ones I know make the source-code publically available.

Once you have source control you can create a repository for each team, when they check in, build their dlls and redistibute to the other teams repositories.


听起来像您不信任您的开发人员-如果是这种情况,请雇用您可以信任的人,即使按小时计算的费用是您的四到五倍.

优秀的人会在信任和支持的环境中蓬勃发展-优秀的开发人员通常生产力更高,即使最初看起来花费更多,也可以为您省钱又省心.

除此之外,我认为您应该认真考虑Keith Barrows的回答:)

问候
Espen Harlinn
Sounds like you don''t trust your developers - if that''s the case, hire somebody you can trust, even if it will cost you four or five times as much on an hourly basis.

Good people thrive in a trusting and supporting environment - good developers are usually far more productive, and will save you both money and grief, even if they initially seem to cost far more.

Apart from that I think you should seriously consider Keith Barrows answer :)

Regards
Espen Harlinn


像Composite UI Block这样的设计方法可能会对您有所帮助.请参见此处 [
A design approach like the Composite UI Block may help you out. See here[^].


这篇关于如何将Web项目拆分为服务器项目的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆