blocks|key|1041004|text|除了将第一个参数硬编码为true的Assert之外，您可以很好地使用它。您可能应该在那里添加一些条件，只有当条件为false时，才会打印消息(第二个参数)。因此，在您的代码示例中，它将永远不会显示。在某些情况下，如果您不想将调试语句包装在条件块中，WriteLineIf可能会派上用场。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1041005|查看Debug+class+reference，它有很多有用的方法和属性来帮助您记录日志。|1041006|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.diagnostics.debug_members.aspx^0|C|4|H|6|3G|B|0|2|L|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

You are using it fine except for <code>Assert</code> with first argument hardcoded to <code>true</code>. You should probably add some condition there and the message (second argument) will be printed only if the condition is false. So in your code example it will never be displayed. In some cases <code>WriteLineIf</code> may come in handy if you don't want to wrap your debug statements in conditional blocks. 

Check out the <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.debug_members.aspx" rel="nofollow noreferrer">Debug class reference</a> it has quite a few useful methods and properties to help you log things.

blocks|key|1256013|text|System.Diagnostics也包含EventLog.WriteEntry，但您可能想要也可能不想用跟踪消息淹没EventLog，尽管这是记录主要应用程序事件的一种简单方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1256014|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

System.Diagnostics also contains EventLog.WriteEntry, but you may or may not want to flood the EventLog with trace messages, though it is an easy way to get major app events logged.

blocks|key|1041137|text|这个回应很晚，但是..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1041138|我认为你应该考虑使用TraceSources而不是Debug.WriteLine和/或Trace.WriteLine。使用TraceSources，您可以实现对日志的更高级别的控制。可以控制每个TraceSource的级别，也可以控制TraceSource的目的地(TraceListener)。您可以像这样编写代码：|1041139|public+class+RectToSqlServer+:+IDatabaseUtilities
{
++private+static+readonly+TraceSource+ts+=+new+TraceSource("RectToSqlServer");

++public+void+AddRectToDatabase(object+record)
++{
++++ts.TraceEvent(TraceEventType.Information,+"record+=+{0}",+record.ToString());

++++//Add+record+to+database+...

++}
}

public+class+RectToOracle+:+IDatabaseUtilities
{
++private+static+readonly+TraceSource+ts+=+new+TraceSource("RectToOracleServer");

++public+void+AddRectToDatabase(object+record)
++{
++++ts.TraceEvent(TraceEventType.Information,+"record+=+{0}",+record.ToString());

++++//Add+record+to+database+...

++}
}|code-block|syntax|javascript|1041140|现在，您可以独立地控制每个类的日志记录(级别、目标等)。此外，请注意，您不必同时添加Trace.WriteLine和Debug.WriteLine才能在调试和发布版本中获得日志记录。使用TraceSources将使您在将来使用ETW时处于有利地位，因为从.NET+(可能是3.5版本，肯定是4.0版本)开始就有了可用的ETWTraceListener。但这种特殊的ETW功能只在Vista和更高版本的操作系统上可用。|1041141|要向System.Diagnostics添加功能(主要是-可能仅限于-如果通过TraceSource进行日志记录)，请查看Ukadc.Diagnostics。Ukadc.Diagnostics向System.Diagnostics添加了非常酷的格式化功能(类似于您可以使用log4net和NLog执行的操作)。没有代码依赖性(只需安装Ukadc.Diagnostics并在您的app.config中添加一些配置)。我不得不说，我认为这真的很酷。|offset|length|1041142|如果您想花点功夫来包装对TraceSources的访问，请参阅here，了解一个有趣的TraceSource包装器实现，它实质上使TraceSources能够从“祖先”TraceSources“继承”日志记录配置(就像log4net和NLog记录器如何继承日志记录设置一样)。|1041143|entityMap|0|LINK|mutability|MUTABLE|url|http://ukadcdiagnostics.codeplex.com/|1|http://github.com/castleproject/Castle.Core/blob/master/src/Castle.Core/Core/Logging/TraceLogger.cs^0|0|0|0|0|1P|H|0|0|V|4|1|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@$M|15|N|16|1|17]]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@$M|19|N|1A|1|1B]]|A|$]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

This response is late, but ...

I think you should consider using TraceSources rather than Debug.WriteLine and/or Trace.WriteLine. With TraceSources, you can achieve a higher level of control over your logging. The level of each TraceSource can be controlled as can the destination of the TraceSource (TraceListener). You can write code like this:

<pre><code>public class RectToSqlServer : IDatabaseUtilities
{
 private static readonly TraceSource ts = new TraceSource("RectToSqlServer");

 public void AddRectToDatabase(object record)
 {
 ts.TraceEvent(TraceEventType.Information, "record = {0}", record.ToString());

 //Add record to database ...

 }
}

public class RectToOracle : IDatabaseUtilities
{
 private static readonly TraceSource ts = new TraceSource("RectToOracleServer");

 public void AddRectToDatabase(object record)
 {
 ts.TraceEvent(TraceEventType.Information, "record = {0}", record.ToString());

 //Add record to database ...

 }
}
</code></pre>

Now, you can control the logging (level, destination, etc) for each class independently. Also, note that you don't have to add both Trace.WriteLine and Debug.WriteLine to get logging in both debug and release builds. Using TraceSources will put you in a good position to use ETW in the future as there is an ETWTraceListener available starting in .NET (maybe 3.5, certainly by 4.0). BUT this particular ETW functionality is only available on Vista and later OS's. 

To add capability to System.Diagnostics (primarily - maybe only - if logging via TraceSource), look at <a href="http://ukadcdiagnostics.codeplex.com/" rel="nofollow">Ukadc.Diagnostics</a>. Ukadc.Diagnostics adds pretty cool formatting capability (similar to what you can do with log4net and NLog) to System.Diagnostics. There is no code dependency (just install Ukadc.Diagnostics and add some configuration to your app.config). I have to say that I think it is really cool.

If you want to put in a little work to wrap your access to TraceSources, see <a href="http://github.com/castleproject/Castle.Core/blob/master/src/Castle.Core/Core/Logging/TraceLogger.cs" rel="nofollow">here</a> for an interesting implementation of a TraceSource wrapper that essentially gives TraceSources the ability to "inherit" logging configuration from "ancestor" TraceSources (like how log4net and NLog loggers can inherit logging settings).

We initially didn't use any logging or debug tracing but after spending few weeks to trace down some data corruption we decided to put required Debug.Write and Trace for production and Debug.Assert

So now question is What is the best practice to use debug and trace logging. I am just looking for some thing generic.

<pre><code>public void AddRectodatabase(object record)
{
 Debug.WriteLine(record.ToString());
 Trace.WriteLine(record.ToString());

 // Add it to databse

 Debug.Assert(true, "Use this on case by case basis");
}
</code></pre>

Is this good enough for general purpose, am i doing anything wrong in there?

We want to stick with .net System.Diagnostics over other alternatives like log4net.

Is there any thing else useful in System.Diagnostics?

.net Diagnostics best practices?

我们最初没有使用任何日志记录或调试跟踪，但在花了几周时间来跟踪一些数据损坏后，我们决定将生产和Debug.Assert所需的Debug.Write和跟踪因此，现在的问题是使用调试和跟踪日志记录的最佳实践是什么。我只是在找一些通用的东西。public void AddRectodatabase(object record...

问.net诊断最佳实践？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.net诊断最佳实践？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.net诊断最佳实践？
EN