blocks|key|359680|text|主要区别在于您所指出的:发布中不包含调试，而跟踪中包含。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359681|据我所知，预期的不同之处在于，开发团队可能会使用Debug发出丰富的描述性消息，这些消息可能对产品的使用者来说过于详细(或揭示)，而Trace的目的是发出更具体地适用于检测应用程序的消息。|359682|为了回答您的最后一个问题，我想不出使用Debug来检测我打算发布的代码片段的理由。|359683|希望这能有所帮助。|359684|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

The main difference is the one you indicate: Debug is not included in release, while Trace is.

The intended difference, as I understand it, is that development teams might use Debug to emit rich, descriptive messages that might prove too detailed (or revealing) for the consumer(s) of a product, while Trace is intended to emit the kinds of messages that are more specifically geared toward instrumenting an application.

To answer your last question, I can't think of a reason to use Debug to instrument a piece of code I intended to release.

Hope this helps.

blocks|key|3151036|text|跟踪和调试之间的唯一区别是，在将程序编译为发布版本时，跟踪语句默认情况下包含在程序中，而调试语句则不包含。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3151037|因此，debug类主要用于开发阶段的调试，而trace可用于编译和发布应用程序后的测试和优化。|offset|length|style|BOLD|3151038|entityMap^0|0|15|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

The only difference between trace and debug is that trace statements are included by default in the program when it is compiled into a release build, whereas debug statement are not.

Thus, the debug class is principally used for debugging in the development phase, while trace can be used for testing and optimization after the application is compiled and released.

blocks|key|361014|text|调试用于纯粹的调试目的。它在调试执行(调试模式)中发出丰富的消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361015|跟踪有助于应用程序调试、错误修复和分析(在发布之后)。|361016|Debug类在发布模式下没有用处。|361017|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Debug is used to pure debugging purposes. It emits rich messages in debug execution (debug mode).

Trace helps in application debugging, bug fixing, and profiling (after release).

The Debug class is of no use in release mode.

blocks|key|3363786|text|我会考虑使用log4net进行跟踪，因为它的功能更加灵活和健壮。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3363787|但对于真正的调试消息，除了我自己或内部测试人员之外，我永远不会让任何人看到，我可能会坚持使用Debug。|3363788|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'd look at using log4net for tracing as its capabilities are much more flexible and robust.

But for true debug messages that I never intend for anyone other than me or an internal tester to see, I'd probably stick with Debug.

blocks|key|361763|text|对于高度性能敏感的代码块，将Trace保留为已编译但禁用可能会产生性能差异。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361764|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|$]]

For highly performance sensitive code blocks, leaving Trace compiled-in but disabled might make a performance difference.

blocks|key|359778|text|跟踪和调试之间的完全区别：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359779|359780|调试和跟踪都使用System.Diagnostics命名空间。|blockquote|359781|359782|调试|359783|359784|359785|它使用调试类。它在调试版本中使用|unordered-list-item|359786|。|359787|它使用应用程序的时间|359788|调试模式编译器在executable.|359789|Debug类中插入一些调试代码仅在调试时工作mode.|359790|Performance分析不能使用Debug.|359791|Debugging来查找程序中的错误。对于调试，我们可以使用method.|359792|Debug+()+Debug.Write()作为主程序执行运行在同一线程中。|359793|<+code+>F221|359794|跟踪|359795|359796|它使用跟踪类。默认情况下，当程序编译为已发布版本时，|359797|跟踪语句包含。|359798|跟踪类用于测试和优化，即使在编译应用程序之后，released.|359799|Trace类在调试模式和发布模式下都有效。|359800|跟踪在不同于主程序执行线程的线程中运行。|359801|H133对于跟踪，我们可以使用Trace.Write()方法。<代码>H234<代码>H135它使用应用程序部署时间。<代码>H236<代码>F237|359802|参考：C#+Corner|offset|length|359803|entityMap|0|LINK|mutability|MUTABLE|url|https://www.c-sharpcorner.com/blogs/difference-between-debug-and-trace1^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|3|9|0|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1W|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|21|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|22|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|23|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|24|8|@]|9|@]|A|$]]|$1|T|3|U|5|M|7|25|8|@]|9|@]|A|$]]|$1|V|3|W|5|M|7|26|8|@]|9|@]|A|$]]|$1|X|3|Y|5|M|7|27|8|@]|9|@]|A|$]]|$1|Z|3|10|5|M|7|28|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|29|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2A|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|16|3|17|5|M|7|2C|8|@]|9|@]|A|$]]|$1|18|3|19|5|M|7|2D|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|M|7|2E|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|M|7|2F|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|M|7|2G|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2H|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2I|8|@]|9|@$1K|2J|1L|2K|1|2L]]|A|$]]|$1|1M|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]]|1N|$1O|$5|1P|1Q|1R|A|$1S|1T]]]]

Full difference between Trace and Debug:
<blockquote>
Both Debug and Trace use System.Diagnostics namespace.
Debug
<ul>
<li>It uses Debug class.</li>
<li>It uses in debug build.</li>
<li>It uses the time of application development.</li>
<li>In Debug mode compiler inserts some debugging code inside the executable.</li>
<li>Debug class works only in debug mode.</li>
<li>Performance analysis cannot be done using Debug.</li>
<li>Debugging uses to find error in program.</li>
<li>For Debug we can use Debug.Write() method.</li>
<li>Debug runs in same thread as main program execute.</li>
</ul>
Trace
<ul>
<li>It uses Trace class.</li>
<li>Trace statement includes by default when program compiled into released build.</li>
<li>Trace class is used for testing and optimization even after an application is compiled and released.</li>
<li>Trace class works in both case Debug mode as well as release mode.</li>
<li>Trace runs in different thread form main program execute thread.</li>
<li>For Trace we can use Trace.Write() method.</li>
<li>It uses time of application deployment.</li>
</ul>
</blockquote>
Reference: <a href="https://www.c-sharpcorner.com/blogs/difference-between-debug-and-trace1" rel="nofollow noreferrer">C# Corner</a>

blocks|key|3363946|text|你已经回答了你自己的问题。如果调试消息留在里面，人们就可以看到它们。例如，假设您这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3363947|Debug.WriteLine("Connecting+to+DB+with+username:+blah+and+PW:+pass");|code-block|syntax|javascript|3363948|任何反编译你的代码的人都能看到这一点。但这可能是您在测试过程中需要了解的非常重要的事情。|3363949|跟踪是不同的。如果你要做跟踪，我可能会直接使用log4net。|3363950|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You've answered your own question. If Debug messages stayed in, people could see them. For example, let's say you do:
<pre class="lang-cs prettyprint-override"><code>Debug.WriteLine(&quot;Connecting to DB with username: blah and PW: pass&quot;);
</code></pre>
Anyone who decompiles your code can see that. But that may be something vitally important for you to know during testing.
Trace is different. If you are going to do Trace, I'd likely just use log4net.

It seems that the 

<ul>
<li><a href="https://msdn.microsoft.com/en-us/library/system.diagnostics.debug(v=vs.110).aspx" rel="noreferrer"><code>System.Diagnostics.Debug</code></a>, and </li>
<li><a href="https://msdn.microsoft.com/en-us/library/system.diagnostics.trace(v=vs.110).aspx" rel="noreferrer"><code>System.Diagnostics.Trace</code></a> </li>
</ul>

are largely the same, with the notable exception that Debug usage is compiled out in a release configuration. 

When would you use one and not the other? The only answer to this I've dug up so far is just that you use the Debug class to generate output that you only see in debug configuration, and Trace will remain in a release configuration, but that doesn't really answer the question in my head.

If you're going to instrument your code, why would you ever use Debug, since Trace can be turned off without a recompile?

Trace vs Debug in .NET BCL

看起来，，和 在很大程度上是相同的，但值得注意的例外是，调试的使用是在发布配置中编译出来的。什么时候你会使用其中一个而不使用另一个？到目前为止，我找到的唯一答案是，您使用跟踪调试类来生成仅在调试配置中看到的输出，将保留在发布配置中，但这并不能真正回答我脑海中的问题。如果你打算检测你的代码，为什么要使用调试，因为跟踪可以在不重新编译的情况下被关闭？

问.NET BCL中的跟踪与调试
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET BCL中的跟踪与调试EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET BCL中的跟踪与调试
EN