http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspxIn my previous post I mentioned that CLR 4.0 will support managed dump debugging through ICorDebug, and that to do this we had to re-architect the debugging support in the CLR. I want to give you a little more detail about what we've been doing here.en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#10120302Wed, 26 Jan 2011 01:54:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:10120302Rick Byers - exMSFT<p>Raymond: yes it&#39;s still needed for any &#39;execution control&#39; operations (stepping, breakpoints, etc.) because so far we&#39;ve only moved inspection over to the new out-of-process model. &nbsp;Moving more things to the new model continues to be a priority for the team.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10120302" width="1" height="1">http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#10097058Fri, 26 Nov 2010 13:33:54 GMT91d46819-8472-40ad-a661-2c78acb4018c:10097058Raymond<p>I tried using VS2010 to debug a .net4 C# application. I found the DebuggerRCThread is still running and it can&#39;t be suspended. So why the debugger helper thread is still needed?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10097058" width="1" height="1">http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#9051064Fri, 07 Nov 2008 03:49:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:9051064gOODiDEA<p>.NETWhat'sNewintheBCLin.NET4.0NetMonAPI–Capture,ParseandandCaptureFileAccess(wi...</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9051064" width="1" height="1">http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#9051058Fri, 07 Nov 2008 03:46:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:9051058gOODiDEA.NET<p>.NET What's New in the BCL in .NET 4.0 NetMon API &amp;#8211; Capture, Parse and and Capture File Access</p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9051058" width="1" height="1">http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#9034371Mon, 03 Nov 2008 21:36:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:9034371Rick Byers - exMSFT<p>Great question! &nbsp;Technically, no this post about the ICD re-arch does NOT mean that x64 mixed-mode will be available. &nbsp;It's true that the principles I mentioned (particularily managed debugging being supported as a utility library on top of native debuggers) would lead to mixed-mode debugging almost &quot;for free&quot;. &nbsp;But, I also mentioned that for CLR V4 only inspection operations are supported in out-of-process mode. &nbsp;So you could fairly easily build a native debugger that could view managed state (callstacks, args, etc), but you couldn't easily step between them etc.</p> <p>HOWEVER, we heard the customer requests loud and clear for x64-mixed-mode, and appreciate how important it is for you, and so we have indeed added support for it in CLR V4 independent from this re-architecture. &nbsp;See this post for more details: <a rel="nofollow" target="_new" href="http://blogs.msdn.com/rmbyers/archive/2008/10/30/clr-4-0-advancements-in-diagnostics.aspx">http://blogs.msdn.com/rmbyers/archive/2008/10/30/clr-4-0-advancements-in-diagnostics.aspx</a></p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9034371" width="1" height="1">http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx#9028334Sat, 01 Nov 2008 20:13:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:9028334jabbera<p>Does this mean that 64 bit mixed mode debugging will be supported?</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9028334" width="1" height="1">