blocks|key|1831224|text|好吧，值得注意的是，它们的意思完全不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1831225|如果没有定义调试符号，那么在第一种情况下，SetPrivateValue本身将不会被调用...而在第二种情况下，它将存在，但任何未使用DEBUG符号编译的调用方都将省略这些调用。|offset|length|style|CODE|1831226|如果代码及其所有调用方都在同一个程序集中，那么这种差异就不那么重要了--但这意味着在第一种情况下，您还需要在调用代码周围使用#if+DEBUG。|1831227|就我个人而言，我会推荐第二种方法--但你确实需要在头脑中保持它们之间的区别。|1831228|entityMap^0|0|L|F|0|1Q|9|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

Well, it's worth noting that they don't mean the same thing at all.

If the DEBUG symbol isn't defined, then in the first case the <code>SetPrivateValue</code> itself won't be called... whereas in the second case it will exist, but any callers who are compiled without the DEBUG symbol will have those calls omitted.

If the code and all its callers are in the same assembly this difference is less important - but it means that in the first case you also need to have <code>#if DEBUG</code> around the calling code as well.

Personally I'd recommend the second approach - but you do need to keep the difference between them clear in your head.

blocks|key|1831262|text|在第一个示例中，如果未定义DEBUG，则SetPrivateValue将不存在于构建中；在第二个示例中，如果未定义DEBUG，则调用到SetPrivateValue将不存在于构建中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|1831263|在第一个示例中，您还必须用#if+DEBUG包装所有对SetPrivateValue的调用。|1831264|在第二个示例中，将省略对SetPrivateValue的调用，但请注意，SetPrivateValue本身仍将被编译。如果您正在构建一个库，这将非常有用，这样引用您的库的应用程序仍然可以使用您的函数(如果满足条件)。|1831265|如果您想省略调用并节省被调用者的空间，您可以使用这两种技术的组合：|1831266|[System.Diagnostics.Conditional("DEBUG")]
public+void+SetPrivateValue(int+value){
++++#if+DEBUG
++++//+method+body+here
++++#endif
}|code-block|syntax|javascript|1831267|entityMap^0|D|5|K|F|1L|5|1V|F|1S|2|0|D|9|R|F|0|C|F|10|F|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|E|@]|F|$]]|$1|I|3|J|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|E|@]|F|$]]|$1|K|3|L|5|6|7|1E|8|@]|E|@]|F|$]]|$1|M|3|N|5|O|7|1F|8|@]|E|@]|F|$P|Q]]|$1|R|3|-4|5|6|7|1G|8|@]|E|@]|F|$]]]|S|$]]

With the first example, <code>SetPrivateValue</code> won't exist in the build if <code>DEBUG</code> is not defined, with the second example, calls to <code>SetPrivateValue</code> won't exist in the build if <code>DEBUG</code> is not defined.

With the first example, you'll have to wrap any calls to <code>SetPrivateValue</code> with <code>#if DEBUG</code> as well.

With the second example, the calls to <code>SetPrivateValue</code> will be omitted, but be aware that <code>SetPrivateValue</code> itself will still be compiled. This is useful if you're building a library, so an application referencing your library can still use your function (if the condition is met).

If you want to omit the calls and save the space of the callee, you could use a combination of the two techniques:

<pre><code>[System.Diagnostics.Conditional("DEBUG")]
public void SetPrivateValue(int value){
 #if DEBUG
 // method body here
 #endif
}
</code></pre>

blocks|key|4540948|text|让我们假设您的代码也有一个#else语句，该语句定义了一个空的存根函数，解决了Jon+Skeet的一个问题。这两者之间还有第二个重要的区别。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4540949|假设#if+DEBUG或Conditional函数存在于主项目可执行文件引用的DLL中。使用#if，将根据库的编译设置执行条件评估。使用Conditional属性，将根据调用者的编译设置执行条件计算。|4540950|entityMap^0|D|5|0|2|9|C|B|1A|3|1W|B|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

Let's presume your code also had an <code>#else</code> statement which defined a null stub function, addressing one of Jon Skeet's points. There's a second important distinction between the two.

Suppose the <code>#if DEBUG</code> or <code>Conditional</code> function exists in a DLL which is referenced by your main project executable. Using the <code>#if</code>, the evaluation of the conditional will be performed with regard to the library's compilation settings. Using the <code>Conditional</code> attribute, the evaluation of the conditional will be performed with regard to the compilation settings of the invoker.

blocks|key|1827880|text|我相信很多人不会同意我的观点，但作为一个构建人员，我经常听到“但它在我的机器上工作！”，我的立场是，你几乎不应该使用任何一个。如果您确实需要用于测试和调试，请找出一种方法，使可测试性与实际生产代码分离。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1827881|在单元测试中使用mocking抽象场景，为您想要测试的一个场景创建一个单独的版本，但不要将调试测试放到您为生产版本测试和编写的二进制代码中。这些调试测试只是对开发人员隐藏了可能的bug，因此直到过程的后期才能发现它们。|1827882|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'm sure plenty will disagree with me, but having spent time as a build guy constantly hearing "But it works on my machine!", I take the standpoint that you should pretty much never use either. If you really need something for testing and debugging, figure out a way to make that testability seperate from the actual production code.

Abstract the scenarios with mocking in unit tests, make one off versions of things for one off scenarios you want to test, but don't put tests for debug into the code for binaries which you test and write for production release. These debug tests just hide possible bugs from devs so they aren't found until later in the process.

blocks|key|3130772|text|我有一个使用自定义[TraceExtension]记录网络流量的SOAP+WebService扩展。我只在调试构建中使用它，而在Release构建中省略了它。使用#if+DEBUG包装[TraceExtension]属性，从而将其从Release构建中删除。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|3130773|#if+DEBUG
[TraceExtension]
#endif
[System.Web.Service.Protocols.SoapDocumentMethodAttribute(+...+)]
[+more+attributes+...]
public+DatabaseResponse[]+GetDatabaseResponse(+...)+
{
++++object[]+results+=+this.Invoke("GetDatabaseResponse",new+object[]+{
++++++++++...+parmeters}};
}

#if+DEBUG
[TraceExtension]
#endif
public+System.IAsyncResult+BeginGetDatabaseResponse(...)

#if+DEBUG
[TraceExtension]
#endif
public+DatabaseResponse[]+EndGetDatabaseResponse(...)|code-block|syntax|javascript|3130774|entityMap^0|9|G|29|9|2K|G|1H|2|1S|7|38|7|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|D]|$9|W|A|X|B|D]|$9|Y|A|Z|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|10|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|11|8|@]|E|@]|F|$]]]|M|$]]

I have a SOAP WebService extension to log network traffic using a custom <code>[TraceExtension]</code>. I use this only for Debug builds and omit from Release builds. Use the <code>#if DEBUG</code> to wrap the <code>[TraceExtension]</code> attribute thus removing it from Release builds.

<pre><code>#if DEBUG
[TraceExtension]
#endif
[System.Web.Service.Protocols.SoapDocumentMethodAttribute( ... )]
[ more attributes ...]
public DatabaseResponse[] GetDatabaseResponse( ...) 
{
 object[] results = this.Invoke("GetDatabaseResponse",new object[] {
 ... parmeters}};
}

#if DEBUG
[TraceExtension]
#endif
public System.IAsyncResult BeginGetDatabaseResponse(...)

#if DEBUG
[TraceExtension]
#endif
public DatabaseResponse[] EndGetDatabaseResponse(...)
</code></pre>

blocks|key|1827895|text|这一点也很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1827896|if+(Debugger.IsAttached)
{
...
}|code-block|syntax|javascript|1827897|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This one can be useful as well:

<pre><code>if (Debugger.IsAttached)
{
...
}
</code></pre>

blocks|key|1827903|text|通常，您需要在Program.cs中使用它，因为您需要决定在非调试代码上运行调试，而且通常在Windows+Services中也是如此。所以我创建了一个只读字段IsDebugMode，并在静态构造函数中设置了它的值，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1827904|static+class+Program
{

++++#region+Private+variable
++++static+readonly+bool+IsDebugMode+=+false;
++++#endregion+Private+variable

++++#region+Constrcutors
++++static+Program()
++++{
+#if+DEBUG
++++++++IsDebugMode+=+true;
+#endif
++++}
++++#endregion

++++#region+Main

++++///+<summary>
++++///+The+main+entry+point+for+the+application.
++++///+</summary>
++++static+void+Main(string[]+args)
++++{

++++++++if+(IsDebugMode)
++++++++{
++++++++++++MyService+myService+=+new+MyService(args);
++++++++++++myService.OnDebug();+++++++++++++
++++++++}
++++++++else
++++++++{
++++++++++++ServiceBase[]+services+=+new+ServiceBase[]+{+new+MyService+(args)+};
++++++++++++services.Run(args);
++++++++}
++++}

++++#endregion+Main++++++++
}|code-block|syntax|javascript|1827905|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Usually you would need it in Program.cs where you want to decide to run either Debug on Non-Debug code and that too mostly in Windows Services. So I created a readonly field IsDebugMode and set its value in static constructor as shown below.

<pre><code>static class Program
{

 #region Private variable
 static readonly bool IsDebugMode = false;
 #endregion Private variable

 #region Constrcutors
 static Program()
 {
 #if DEBUG
 IsDebugMode = true;
 #endif
 }
 #endregion

 #region Main

 /// &lt;summary&gt;
 /// The main entry point for the application.
 /// &lt;/summary&gt;
 static void Main(string[] args)
 {

 if (IsDebugMode)
 {
 MyService myService = new MyService(args);
 myService.OnDebug(); 
 }
 else
 {
 ServiceBase[] services = new ServiceBase[] { new MyService (args) };
 services.Run(args);
 }
 }

 #endregion Main 
}
</code></pre>

Which is better to use, and why, on a large project:

<pre><code>#if DEBUG
 public void SetPrivateValue(int value)
 { ... }
#endif
</code></pre>

or

<pre><code>[System.Diagnostics.Conditional("DEBUG")]
public void SetPrivateValue(int value)
{ ... }
</code></pre>

#if DEBUG vs. Conditional("DEBUG")

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在大型项目中，使用哪个更好，以及为什么：#if DEBUG    public void SetPrivateValue(int value)    { ... }#endif或[System.Diagnostics.Conditional("DEBUG")]public void SetPrivateValue(in...

问#if DEBUG vs. s. Conditional("DEBUG")
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问#if DEBUG vs. s. Conditional("DEBUG")EN