#.NET REFLECTOR 9 KEY CODE#

Sometimes the Autos window will show additional relevant variables that the Locals window doesn't and vice versa, so you may want to check both if you don't find what you're looking for.

The Locals window shows values from the current stack frame as you double-click each frame in the Call Stack pane. Instead of dropping into SOS mode to look at local variables and the value of this, I simply pull up the Locals debug window. Yes, you can set breakpoints on assemblies that you don't even have the source for.

#.NET REFLECTOR 9 KEY CODE#

You can also set breakpoints on code from within Reflector, which is a bit friendlier than setting breakpoints from the Disassembly window. One cool thing about this is that your Reflector instance stays open the whole time, and as you bounce around your call stack using Go To Reflector, the Reflector instance synchronizes to the new location that you specified using Go To Reflector. You can also Go To Reflector from any frame in a call stack: You may want to first take a look at what Mike's doing to put this in context.ДЇirst I use Jamie Cansdale's awesome TestDriven.NET which has the very cool Go To Reflector feature. I've been doing a similar style of debugging lately that I think is a bit more efficient, and here's how I do it. Mike Taulty recently posted about how he debugs using Visual Studio, Reflector, and SOS.

.net reflector 9 key