<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tracing in ASP.NET Web API</title><link>http://asp.net</link><pubDate>Wed, 27 Feb 2013 14:38:06 GMT</pubDate><generator>umbraco</generator><description>Comments for Tracing in ASP.NET Web API</description><language>en</language><atom:link href="http://asp.net/rss/comments/38202" rel="self" type="application/rss+xml" /><item><title>Comment Posted by obayani</title><link>http://asp.net/web-api/overview/testing-and-debugging/tracing-in-aspnet-web-api</link><pubDate>Thu, 07 Jun 2012 09:03:19 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000015716</guid><description><![CDATA[ <p>Excellent article Mike.</p><p></p><p>I have a question: why just not use System.Diagnostics.Trace.WriteLine (or the Debug one if you need to remove tracing in release) or any other logging api directly? I agree that replacing the default trace manager is better and more streamlined but putting a simple Trace.WriteLine is more straightforward and simple. Nevertheless, the use of one or the other methods must be discussed according to the development constraints which are different between projects.</p>]]></description><enclosure length="0" type="image/png" url="http://i1.asp.net/avatar/obayani.jpg?forceidenticon=false&amp;dt=635050543200000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item><item><title>Comment Posted by MikeWasson</title><link>http://asp.net/web-api/overview/testing-and-debugging/tracing-in-aspnet-web-api</link><pubDate>Wed, 20 Jun 2012 01:16:27 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000015807</guid><description><![CDATA[ <p>obayani: If you want to enable the tracing that is built into the framework, then you need to provide an ITraceWriter implementation. </p><p></p><p>To trace your own code, using Trace.WriteLine is fine. But if you decide later to use another tracing library (like NLog) then you would need to change all of those trace calls. </p><p></p><p> </p>]]></description><enclosure length="0" type="image/png" url="http://i2.asp.net/avatar/MikeWasson.jpg?forceidenticon=false&amp;dt=635050543200000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item><item><title>Comment Posted by MEber</title><link>http://asp.net/web-api/overview/testing-and-debugging/tracing-in-aspnet-web-api</link><pubDate>Thu, 13 Sep 2012 13:14:23 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000016432</guid><description><![CDATA[ <p>Mike -- actually when it comes to debugging services there is no substitute to walking through your code in debug mode!</p>]]></description><enclosure length="0" type="image/png" url="http://i1.asp.net/avatar/MEber.jpg?forceidenticon=false&amp;dt=635050543200000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item><item><title>Comment Posted by joshnoe23</title><link>http://asp.net/web-api/overview/testing-and-debugging/tracing-in-aspnet-web-api</link><pubDate>Mon, 18 Feb 2013 14:38:29 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000018447</guid><description><![CDATA[ <p>How about for logging errors?  Would this be overkill since you can just handle all uncaught errors in the ExceptionFilterAttribute, or does Implementing ITraceWriter still provide some benefit?</p>]]></description><enclosure length="0" type="image/png" url="http://i1.asp.net/avatar/joshnoe23.jpg?forceidenticon=false&amp;dt=635050543200000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item><item><title>Comment Posted by acohen-tempworks</title><link>http://asp.net/web-api/overview/testing-and-debugging/tracing-in-aspnet-web-api</link><pubDate>Wed, 27 Feb 2013 14:38:06 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000018536</guid><description><![CDATA[ <p>When deployed in RELEASE mode, this does not work.  I have an ITraceWriter implementation that uses NLog to write to log files.  This works locally in DEBUG mode.</p>]]></description><enclosure length="0" type="image/png" url="http://i3.asp.net/avatar/acohen-tempworks.jpg?forceidenticon=false&amp;dt=635050543200000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item></channel></rss>