我如何找到哪个缺少的DLL使我的.NET应用程序在启动时崩溃？ [英] How do I find out which missing DLL is making my .NET application crash on startup?

问题描述

当将第三方程序集的依赖项添加到典型的.NET应用程序时，很容易忘记将它们添加到安装程序中。这个问题倾向于只有在安装应用程序之后才会显示出来，并且在启动时会以很少有用的信息随时可用而崩溃。

When dependencies on 3rd party assemblies are added to a typical .NET application it's very easy to forget to add them to the installer. This problem tends to reveal itself only after the application is installed, and in the form of a crash on startup with little helpful information readily available.

什么是最好的工具

推荐答案

完全自动化的构建有助于减少人类组件，因此，错误。如果它是每次自动构建的，你知道每个构建将是一样的，所以一旦你有它的工作一次，它总是工作。

Fully automated builds help reduce the human component and therefore the error. If it's automatically built every time, you know every build will be the same, so once you have it working once, it's always going to work.

我们使用工具， a href =http://msdn.microsoft.com/en-us/library/0k6kkbsd.aspx =nofollow noreferrer> MSBuild 和 CruiseControl.net

We use tools like MSBuild and CruiseControl.net

如果您正在查看对于可帮助您解决崩溃原因的工具，请在装配绑定（Fusion）日志查看器（或fuslogvw）。如果您在启动应用程序之前启动它，那么设置日志文件位置并打开完整日志记录将报告绑定程序集的任何尝试，并列出任何失败。

If you're looking for tools that help your work out the cause of the crash, take a log at the Assembly binding (Fusion) log viewer (or fuslogvw). If you start it up before you start your app, set the log file location and turn full logging on it will report any attempts to bind assemblies, and list any failures.

这篇关于我如何找到哪个缺少的DLL使我的.NET应用程序在启动时崩溃？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！