部署 .net DLL 供 ColdFusion 使用？
我的公司目前运行一个 .net/sharepoint 内部网和一个 ColdFusion 公共网站。有很多重复的功能和笨拙的 Web 服务层用于支持这两个平台。最近，我们一直在探索在 ColdFusion 前端中使用 .net 类，这已经显示出很大的前景。
不过，存在一些与管理 DLL 相关的问题。我们目前只是从服务器上的目录加载 DLL，但似乎一旦 ColdFusion 加载了 DLL，您现在就可以再覆盖 DLL，而无需先停止 Coldfusion .Net 服务。我注意到 ColdFusion 还支持从 GAC 加载类。
对于任何走这条路的人 - 如何管理 ColdFusion 使用的 DLL，特别是更新和部署 DLL？我们应该使用程序集缓存吗？还有其他问题吗？
My company currently runs a .net/sharepoint intranet and a ColdFusion public website. There is a lot of duplicated functionality and clumsy web service layers used to support the two platforms. Recently we have been exploring using .net classes in our ColdFusion front end which has shown a lot of promise.
There are a few issues related to managing the DLLs though. We are currently just loading the DLL from a directory on the server but it seems that once ColdFusion loads the DLL you can now longer overwrite the DLL without first stopping the Coldfusion .Net service. I noticed that ColdFusion also supports loading classes from the GAC.
For anyone who has gone down this route - how so you manage the DLLs that ColdFusion uses, specifically updating and deploying the DLLs? Should we use the assembly cache? Are there any other gotchas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果可能的话，我强烈建议 GAC，只要您自己开发库（您就是这样，因此需要更新它们），这样您就可以强制执行强命名的程序集及其依赖项等。
如果您可以控制某些GAC 的缺点变成了优点，比如程序集像使用已编译的框架而不是已安装的框架一样运行。消除了 .net 框架升级对您的代码产生不利影响的可能性（尽管不太可能）。
使用 GAC 被认为是避免 DLL Hell（依赖地狱）的最佳实践。
http://en.wikipedia.org/wiki/DLL_hell
=)
I would strongly suggest GAC if possible, as long as you're developing the libraries yourself (which you are, thus the need to update them) so you can enforce strongly named assemblies and their dependencies etc.
If you're in control some of the drawbacks of GAC become positives, like the assembly running as it does with the compiled framework rather than the installed one. Removes the chance (even though its unlikely) that a .net framework upgrade is going to adversely affect your code.
Using the GAC is considered best practice to avoid DLL Hell (dependency hell).
http://en.wikipedia.org/wiki/DLL_hell
=)