给GAC 还是不给GAC？私有程序集与共享程序集
从部署的角度来看，我认为 GAC（或共享程序集）的使用使部署过程变得复杂，但没有增加太多好处。
它不仅使新应用程序的安装变得复杂，而且还使该应用程序的“升级”场景变得复杂。
我想我在某处读到，最好尽可能保持程序集“私有”（主程序集和依赖程序集位于同一目录上）。如果多个应用程序使用一个程序集，它们将拥有自己的副本。
使用 GAC 有什么好处（除了可以忽略不计的性能升级）？它会超过未来出现的“配置管理”问题吗？或者如果可能的话，让程序集保持“私有”会更好吗？
（还有，有没有一种情况是被迫使用GAC的？）
谢谢！
PS：我不知道术语“私有”程序集是否正确描述了我正在谈论的配置。 我为此提出了一个单独的问题。
In a deployment perspective, I think that the usage of GAC (or shared assemblies) complicates the deployment process without adding much benefit.
Not only does it complicate the installation of new application, it also complicates the "upgrade" scenario for this applications.
I think I have read somewhere that it is better to keep the assemblies "private" (The main assembly and the dependency assemblies on the same directory) as much as possible. If multiple applications uses an assembly, they will have their own copy of it.
What is the benefit of using the GAC (other than the negligible performance upgrade)? Will it outweight the "configuration management" problems that it will present in the future? Or is it much better to keep the assemblies "private", if possible?
(Also, is there a scenario wherein one is forced to use the GAC?)
Thanks!
PS: I don't know if the term "private" assemblies properly describes the configuration I am talking about. I've opened a separate question for this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论