在对第三方组件的依赖被添加到一个典型的.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.

什么是最好的工具和技术，以找出哪些需要被添加到安装程序组件？

What are the best tools and techniques to find out which assemblies need to be added to the installer?

推荐答案

全自动生成减少了人工干预，因此错误。如果它自动生成每一次，你知道每一个版本将是相同的，所以一旦你拥有了它的工作一次，它总是去上班。

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.

我们使用的工具，如的MSBuild 和的 CruiseControl.net

We use tools like MSBuild and CruiseControl.net

如果你正在寻找的工具，帮助你的工作出了事故的原因，采取了日志中的集绑定（融合）日志查看器（或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.