如何从用户的计算机获取有用的WPF.NET错误信息？-HowcanIgetusefulWPF.NETerrorinformationfromauser'smachine?

14  

The procedure I would use is to handle the UnhandledException event in the app domain.

我将使用的过程是处理应用程序域中的UnhandledException事件。

Once you have done that, you have a number of options. Logging the exception to a file, serialising it for later inspection, showing a dialog box with the exception message.

完成后，您有很多选择。将异常记录到文件中，将其序列化以供以后检查，显示带有异常消息的对话框。

EDIT: XamlParseException's occur when your main window is being created. This means that the constructor of that window is being called. If you perform any logic in that constructor, any resulting exceptions will throw a XamlParseException. It is my understanding that the UnhandledException handler will still catch this exception.

编辑：在创建主窗口时发生XamlParseException。这意味着正在调用该窗口的构造函数。如果在该构造函数中执行任何逻辑，则任何生成的异常都将抛出XamlParseException。据我所知，UnhandledException处理程序仍将捕获此异常。

To hook up the UnhandledException event in WPF, add the event hookup in your app.xaml

要在WPF中连接UnhandledException事件，请在app.xaml中添加事件连接

which then adds a method in your app.cs

然后在app.cs中添加一个方法

public partial class App : Application
{
    void App_DispatcherUnhandledException(object sender, DispatcherUnhandledExceptionEventArgs e)
    {
        // Process unhandled exception do stuff below

        // Prevent default unhandled exception processing
        e.Handled = true;
    }
}

MSDN

MSDN

2  

In addition to having an unhandled exception event handler that logs the stack trace, it is also useful to look at the crash dumps being generated on the repro machine. You mentioned it's Windows 7, so you can look for corresponding crash dumps in the following ways:

除了具有记录堆栈跟踪的未处理异常事件处理程序之外，查看在repro计算机上生成的故障转储也很有用。您提到它是Windows 7，因此您可以通过以下方式查找相应的故障转储：

1. Control Panel -> All Control Panel Items -> Action Center -> "View problems to report" link underneath the Maintenance/"Check for solutions to unreported problems" area. This brings up a list of applications that have crashed and you can drill down into them to find the dump files and information. Look for the "View a temporary copy of these files" link in the bottom left of the problem technical details. This will extract the dump files and show them to you in an explorer window.

   控制面板 - >所有控制面板项目 - >操作中心 - >“查看要报告的问题”链接位于维护/“检查未报告问题的解决方案”区域下方。这将显示已崩溃的应用程序列表，您可以深入查看它们以查找转储文件和信息。查找问题技术详细信息左下角的“查看这些文件的临时副本”链接。这将提取转储文件并在资源管理器窗口中显示给您。

2. cd /d %ProgramData%\Microsoft\Windows\WER.

   cd / d％ProgramData％\ Microsoft \ Windows \ WER。

WER seems to keep it's crash dumps underneath that directory, so what I do is a dir /s/b for part of the app name that I know will be there. For example, I made a on purpose crashy app that i called crashyapp.exe:

WER似乎将它的崩溃转储保存在该目录下，所以我所做的是一个dir / s / b，我知道将在那里使用应用程序名称的一部分。例如，我制作了一个故意崩溃的应用程序，我称之为crashyapp.exe：

C:\ProgramData\Microsoft\Windows\WER>dir /s/b *crashy*
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_crashyapp.exe_56f8d710d72e31d822d6b895c5c43a18d34acfa1_cab_2823e614
    

1  

Exception logging (as in the answer from Alastair Pitts) would be a help in zeroing in on the source of the error.

异常记录（如Alastair Pitts的答案）将有助于归零错误的来源。

The presence of XamlParse on line P9 suggests that there may be a problem initializing a control or window from the XAML description. There may be an assembly referenced by the XAML which was not found on the target computer, or did not match the signature in the XAML.

在P9行上存在XamlParse表明从XAML描述初始化控件或窗口可能存在问题。可能存在由XAML引用的程序集，该程序集在目标计算机上找不到，或者与XAML中的签名不匹配。

Edit:

编辑：

XAML parsing occurs in InitializeComponent() which is called in the constructor of the window or control

XAML解析发生在InitializeComponent（）中，它在窗口或控件的构造函数中调用

0  

In addition to Alistair's answer, it's the InnerException that gave me the clues I was looking for:

除了Alistair的答案之外，还有InnerException给了我寻找的线索：

public partial class App : Application {
    void App_DispatcherUnhandledException(object sender, DispatcherUnhandledExceptionEventArgs e) {
        Exception ex = e.Exception;
        Exception ex_inner = ex.InnerException;
        string msg = ex.Message + "\n\n" + ex.StackTrace + "\n\n" +
            "Inner Exception:\n" + ex_inner.Message + "\n\n" + ex_inner.StackTrace + "\n\n" + 
            Utils.RegistryVersion();
        MessageBox.Show(msg, "Drop Print Batch Application Halted!", MessageBoxButton.OK);
        Utils.MailReport(msg);
        e.Handled = true;
        Application.Current.Shutdown();
    }
}