Tips and suggestions for troubleshooting and debugging WPF

This article covers many techniques you can use to troubleshoot and debug your WPF application, including binding errors, exception handling, inspecting the VisualTree and logging.

Table of Contents

• Introduction
• Binding Errors
  • 1. Changing Trace Level for All in Options
  • 2. Changing Trace Level on a Specific Binding
• WPF Tree Visualizer
  • Other inspection tools
• Inner Exceptions
• Unhandled Exceptions
  • Application.DispatcherUnhandledException
  • AppDomain.CurrentDomain.UnhandledException
  • TaskScheduler.UnobservedTaskException
  • The catch-all Unhandled Handler!
  • Drilling down to include the Inner Exceptions
• Commenting Out and Binary Chopping
• Logging
  • Logging Level
  • Repository Choice
  • Why Reinvent the Wheel
    • Log4Net
    • ELMAH
    • NLog
    • NuGet
• See Also
• Community Resources

Windows Presentation Foundation (WPF) is a joy to develop rich user experiences with. Animations, bindings, reskinnable codeless interfaces, all backed up with traditional .Net programming all make for a very rapid development cycle. However, when something goes wrong in that autogenerated super-sexy front-end, it is not always clear where the problem is. 

This article will cover some of the methods for analyzing your WPF application, troubleshooting issues, and debugging seemingly obscure errors.

Read more: Greg's Cool [Insert Clever Name] of the Day

Read more: Troubleshooting WPF (Debugging WPF)

QR: 

Posted via email from Jasper-net