Log with historical debug (IntelliTrace)

5

I have a WPF application and am looking for the best way to solve unhandled exceptions. Today, when an unexpected exception occurs, deal in event Application.DispatcherUnhandledException . There, I write the Exception.StackTrace , so , at the time of solving, I can look at the methods that were called, in most cases, finding the line where the error occurs is not so complicated (but I want to improve it)

I've heard ( video - it reproduces the error, the IntelliTrace file is saved in a folder, it opens in VS and can debug ) about write historical debug data from IntelliTrace, which would theoretically help too much at the time of debugging and even fixing errors that occur with users but that I can not play in debug .

  • How can I collect IntelliTrace information in my application, not being in debug ?
  • How can I read the collected data?
  • Is it worth migrating from error logs with stack trace to IntelliTrace?
  • What about performance?
asked by anonymous 08.02.2017 / 02:05

1 answer

1

The answers are very long, so I will put the links not to "pollute" the text:

  • How can I collect IntelliTrace information in my application, not being debugged?

    • Using IntelliTrace standalone collector
  •   

    The IntelliTrace standalone collector allows you to collect IntelliTrace diagnostic data for your applications on production servers or in other environments without installing Visual Studio on the target computer and without changing the target system environment

         

    Complete answer: link

  • How can I read the collected data?

    • You should open the .iTrace file in Visual Studio Ultimate
  •   

    To debug with IntelliTrace and go through the code, you must have the corresponding source and symbol files

         

    Complete answer: link

  • Is it worth migrating from error logs with stack trace to IntelliTrace?

    • Depends on the result you get after configuring / viewing the Logs, and the performance impact caused by IntelliTrace
  • What about performance?

    • Basically, it will depend on the configuration you make and the production environment
    • MS Tip: Run the collector only when you think there is a problem or when you can reproduce the problem
    • Optimizing IntelliTrace Collection on Production Server:
      • link
      •   

        Tests have shown a 15% reduction in performance

  • More information:

    15.02.2017 / 13:40