Visual Studio debugging tricks every .NET developer should know

Dror Helper | drorh@oz-code.com | @dhelperhttp://oz-code.com | @oz_code

OzCode’s Technical Evangelist

Developing software since 2002Clean Coder & Test Driven Developer

Pluralsight author

B: blog.drorhelper.comT: @dhelper

About.ME

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

“The process of finding and resolving of defects that prevent correct operation of computer software or a system”

Debugging is:

ComplicatedNever plannedFrustratingStressful

Time consuming

Debugging is:

Know your tools

Debugging time wasters

Cannot reproduce the bugNot knowing where to startStart-to-POI timeMultiple restarts during debug

What caused the problem?

When was the last time it worked?What have changed? What is the difference?What input caused the problem?

Breakpoints

Pause execution - where I tell youSo I can inspect my code

• Always• Conditional• Trace

Fix – Build – Run cycleTo understand how we got thereBecause we’ve just crashed

Why we restart debugging?

Edit & Continue

Bad: Fix-Build-Run cyclesGood: Fix bugs without stopping debuggingBetter: In a single debug runEven Better: Avoid stepping over the bug

Working with Data is Hard

Problem: Data is usually complex• Huge objects• Hierarchies• Collections

Learn More at: https://vimeo.com/185820705

LINQ Debugging

Give it a Tryhttps://github.com/oz-code/OzCodeDemo

Thank You!

@oz_code

http://oz-code.com

@dhelper

http://blog.drorhelper.com