<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Debugger.Log and LogMessage</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/09/28/log-message.aspx</link><description>Calls to Debugger.Log in a debuggee can generate a ICorDebugManagedCallback::LogMessage managed debug event. This is the managed equivalent of kernel32!OutputDebugString . Other managed functions (like Debug.Write ) may degenerate to calls to Debugger</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Why is System.Diagnostic.Debugger class compiled in retail?</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/09/28/log-message.aspx#5817645</link><pubDate>Thu, 01 Nov 2007 20:45:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5817645</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;There&amp;amp;#39;s a good reason that methods on a &amp;amp;quot;System.Diagnostics.Debugger&amp;amp;quot; class are still compiled&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5817645" width="1" height="1"&gt;</description></item><item><title>Debugger.Log vs. OutputDebugString</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/09/28/log-message.aspx#655404</link><pubDate>Mon, 03 Jul 2006 21:12:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:655404</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>Both Debugger.Log and OutputDebugString have some key similarities:&lt;br&gt;&lt;br&gt;The both log string for debugging...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=655404" width="1" height="1"&gt;</description></item><item><title>re: Debugger.Log and LogMessage</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/09/28/log-message.aspx#475331</link><pubDate>Thu, 29 Sep 2005 18:41:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:475331</guid><dc:creator>Mike Stall - MSFT</dc:creator><description>Great! &lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=475331" width="1" height="1"&gt;</description></item><item><title>re: Debugger.Log and LogMessage</title><link>http://blogs.msdn.com/b/jmstall/archive/2005/09/28/log-message.aspx#475277</link><pubDate>Thu, 29 Sep 2005 15:39:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:475277</guid><dc:creator>Brian C. Barnes</dc:creator><description>Works Great. My main app has a TraceListener to look for trace messages from user scripts. When running under my debugger, this TraceListener also echos trace messages using OutputDebugString. My debugging app subscribes to the Log messages, and outputs them to a log window. That way, when running scripts under the debugger, any Trace messages in the script end up going to the debugger. Just what I wanted. Thanks Mike and Rick Byers for help on this.&lt;br&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=475277" width="1" height="1"&gt;</description></item></channel></rss>