Debugging is hard - this is a fact of life. Unfortunately, it’s never planned nor expected. It takes too much time, time we could have spent doing cool stuff - like developing new features for our customers.
But while there are many articles and productivity tools aimed at writing better code – faster, it seems as though it’s impossible to find resources that teach you how to effectively debug your code.
In this talk we’ll explore Visual Studio’s more powerful but lesser known debugging capabilities. We’ll also showcase OzCode and explain how it helps finding and fixing bugs faster.
3. Focus on relevant data
Instantly analyze exceptions
Focus on relevant data Search and Filter collections
Get deep insights into your program
Automate Common Debugging Tasks
4. “The process of finding and resolving of defects
that prevent correct operation of computer
software or a system”
Debugging is:
10. Fix – Build – Run cycle
To understand how we got there
Because we’ve just crashed
Why we restart debugging?
11. Edit & Continue
Bad: Fix-Build-Run cycles
Good: Fix bugs without stopping debugging
Better: In a single debug run
Even Better: Avoid stepping over the bug
12. Working with Data is Hard
Problem: Data is usually complex
• Huge objects
• Hierarchies
• Collections
Learn More at: https://vimeo.com/185820705