<?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>A Tracing Primer - Part II (C) [Mike Rousos]</title><link>http://blogs.msdn.com/b/bclteam/archive/2005/09/21/472049.aspx</link><description>In my introduction to tracing ( http://blogs.msdn.com/bclteam/archive/2005/03/15/396431.aspx ), I outlined the basics of how to use TraceSources, TraceListeners, and SourceSwitches to trace the flow of an application. I also covered how to configure Whidbey</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Logging Application Block Intro (Tracing Primer)</title><link>http://blogs.msdn.com/b/bclteam/archive/2005/09/21/472049.aspx#1891416</link><pubDate>Fri, 16 Mar 2007 05:57:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1891416</guid><dc:creator>Humprey Evangelista Cogay</dc:creator><description>&lt;p&gt;We have an applciation (Bought from another company) that has a very good logging system, and during&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1891416" width="1" height="1"&gt;</description></item><item><title>Trace sources in WPF</title><link>http://blogs.msdn.com/b/bclteam/archive/2005/09/21/472049.aspx#756377</link><pubDate>Fri, 15 Sep 2006 22:14:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:756377</guid><dc:creator>Mike Hillberg's Blog on WPF (Avalon)</dc:creator><description>WPF (Avalon) uses the .Net tracing system to provide some diagnostics about what’s going on inside your WPF application. &amp;nbsp;It’s not at all an exhaustive set of traces, and in fact it’s still pretty rudimentary. &amp;nbsp;But frequently it’s enough to help out when&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=756377" width="1" height="1"&gt;</description></item><item><title>Trace sources in WPF</title><link>http://blogs.msdn.com/b/bclteam/archive/2005/09/21/472049.aspx#754239</link><pubDate>Thu, 14 Sep 2006 19:31:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:754239</guid><dc:creator>Mike Hillberg's Blog on WPF (Avalon)</dc:creator><description>WPF (Avalon) uses the .Net tracing system to provide some diagnostics about what’s going on inside your WPF application. &amp;nbsp;It’s not at all an exhaustive set of traces, and in fact it’s still pretty rudimentary. &amp;nbsp;But frequently it’s enough to help out when&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=754239" width="1" height="1"&gt;</description></item><item><title>re: A Tracing Primer - Part II (C) [Mike Rousos]</title><link>http://blogs.msdn.com/b/bclteam/archive/2005/09/21/472049.aspx#472115</link><pubDate>Wed, 21 Sep 2005 04:10:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:472115</guid><dc:creator>Joshua Flanagan</dc:creator><description>Did you consider making the relative paths work both ways, depending on the app?&lt;br&gt;&lt;br&gt;if (HttpContext.Current == null){&lt;br&gt; relativePath = WorkingDirectory;&lt;br&gt;}&lt;br&gt;else {&lt;br&gt; relativePath = ConfigFileDirectory&lt;br&gt;}&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=472115" width="1" height="1"&gt;</description></item></channel></rss>