Practical .NET

Quick Tip: Read the Inner Exception!

That's often where the real problem is.

Another short tip, but, potentially the best one you'll ever get (at least, from me).

When you're debugging and you get an exception, always, always, always click on the View Details link to open the View Details dialog.

If the message in the dialog isn't expanded, expand it, then scan down to the Inner Exception entry. Sometimes it's null, but more often than not, that's where the original problem (and the one you have to fix) is described.

In fact, it's often worthwhile to expand the Inner Exception and read its Inner Exception property.

More Practical .NET Debugging Tips from Peter Vogel:

About the Author

Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.

comments powered by Disqus

Featured

  • Multi-Class Classification Using PyTorch: Model Accuracy

    Dr. James McCaffrey of Microsoft Research continues his four-part series on multi-class classification, designed to predict a value that can be one of three or more possible discrete values, by explaining model accuracy.

  • Python in VS Code Adds Data Viewer for Debugging

    The January 2021 update to the Python Extension for Visual Studio Code is out with a short list of new features headed by a data viewer used while debugging.

  • GitHub Ships Enterprise Server 3.0 Release Candidate

    It's described as "the biggest ever change to Enterprise Server," with improvements to Actions, Packages, mobile, security and more.

  • Attacks on .NET Apps Grow in Number, Severity, Says Security Firm

    .NET apps were found to have more serious vulnerabilities and suffer more attacks last year, according to data gathered by Contrast Labs.

Upcoming Events