I compared source-level stepping perf between Everett and Whidbey here . In both cases, the step operation is implemented by single-stepping through disassembly until you get off the current line. This can result in a lot of single-step operations and...

We’ve made Interop-debugging (aka “mixed-mode debugging”) much faster and more stable in Whidbey (VS8) than it was in Everett (VS7). Interop-stepping was very slow in Everett. One way to measure this is to step over a line like this: int x = GetCount...

Sometimes you may have functions that you don’t want a debugger to step into (such as 3rd-party library code or even your own helper functions like certain getters or ToString calls). I blogged here about debugging “Just-my-code” on a per-function basis...

I've had great experiences with MSDN responding to feedback and improving the docs. At the bottom of each MSDN page is a little hyperlink that says "What did you think of this topic?" and then is a mailto link that makes it very easy to send feedback...

Today, ICorDebug is not documented on MSDN, even though it’s a public API. Your best bet is a few random MSDN articles and some other scattered resources I list here . In fact, search MSDN (as of Jun 6, '05) for “ICorDebugILFrame” and it comes up empty...

I had a sample GUI extension for Mdbg Beta 1. However, it doesn’t build with Mdbg Beta 2 because: 1) we renamed some of the mdbg dlls. 2) it depends on mdbg.snk (strong name key) from the mdbg beta 1 sample which is not included in the beta 2 sdk. 3)...

Mdbg is now included in the Whidbey Beta 2 SDK as a tool. The source is not actually included in the SDK, so we’d like to also refresh the Mdbg sample. Mdbg originally compiled to many different dlls (corapi.dll, corapi2.dll, mdbgeng.dll, mdbgext.dll...