MS Ignite, Super Charged Debugging in VS 2017
Tags: ignite day3, microsoft
Created on: Sep 26 2018 (Wed) @ 10:12 AM
Step into specific, nested methods
Tracepoints, Actions, pseudo debugger variables $Function
Inspection, nse (no side effects), i++ in the watch window won't affect the variable in the program flow itself.
ac, always call
$ReturnValue1 2 3
DebuggerDisplay attribute - will be used as an attribute on the class itself
nq, no quotes
Make object Id, for vars that are added to a collection
Debugging in production???
Diagnostics window, memory usage tab, take snapshot
CPU usage, diagnostics window