具有许多DLL的应用程序是一件坏事吗? [英] Are applications with many DLLs a bad thing?

问题描述

我们有一个企业Web应用程序，它确实包含4个编译组件(DLL).一年多以前，我们开始实现更精细的组件，以试图隔离功能，减少耦合并降低重新编译和部署大量代码块的风险.尽管没有人认为这种方法使我们在添加新功能和修补错误时大大提高了灵活性和上市速度，但该应用程序现在由近40个dll组成.我们有一个命名约定，可以很好地识别我们的组件.

We have an enterpise web application that did consist of 4 compiled components (DLLs). Over a year ago, we began implementing more granular components in an attempt to isolate functionality, reduce coupling and reduce the risk of recompiling and deploying massive chunks of code. While no one argues that this approach has given us MUCH improved flexibility and speed to market when adding new functionality and patching bugs, the applications now consists of nearly 40 dlls. We have a naming convention that works well for identifying our components.

我的问题是:具有许多dll的应用程序是否有不利之处(性能，维护等)?

我们正在探索将代码重构为更大的组件的选项，我认为这可能是某种回归...

We are exploring the option of refactoring code into larger components which I think might be a regression of sorts...

推荐答案

我的问题是:有没有缺点(性能，维护，等...)与许多dll?

My question is: Is there any down-side(Performance, maintenance, etc...) to having an application with many dlls?

有很多DLL的缺点?否
DLL过多的缺点?当然可以.

A downside with many DLLs ? No
A downside with too many DLLs ? Sure.

那么多少太多了?

程序集是一种组织方式，例如名称空间和类.命名空间定义逻辑边界，程序集物理边界.

An assembly is an means of organization, like namespaces and classes. Namespaces define logical boundaries, assemblies physical boundaries.

您应该尝试使程序集保持一致，并将其视为系统模块.

You should try to keep assemblies coherent, and view them as system modules.

是的，如果有成百上千的性能问题.但是40岁的时候，我没看到问题.

And yes, there would be a (small) performance problem if you had hundreds of them. But with 40, I don't see a problem.

这篇关于具有许多DLL的应用程序是一件坏事吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！