我更喜欢这样检查它，而不是寻找#define指令:

if (System.Diagnostics.Debugger.IsAttached)
{
   //...
}
else
{
   //...
}

需要注意的是，您当然可以在调试模式下编译和部署一些东西，但仍然没有附加调试器。

我更喜欢这样检查它，而不是寻找#define指令:

if (System.Diagnostics.Debugger.IsAttached)
{
   //...
}
else
{
   //...
}

需要注意的是，您当然可以在调试模式下编译和部署一些东西，但仍然没有附加调试器。

It is worth noting here that one of the most significant differences between conditionally executing code based on #if DEBUG versus if(System.Diagnostics.Debugger.IsAttached) is that the compiler directive changes the code that is compiled. That is, if you have two different statements in an #if DEBUG/#else/#endif conditional block, only one of them will appear in the compiled code. This is an important distinction because it allows you do do things such as conditionally compile method definitions to be public void mymethod() versus internal void mymethod() depending on build type so that you can, for example, run unit tests on debug builds that will not break access control on production builds, or conditionally compile helper functions in debug builds that will not appear in the final code if they would violate security in some way should they escape into the wild. The IsAttached property, on the other hand, does not affect the compiled code. Both sets of code are in all of the builds - the IsAttached condition will only affect what is executed. This by itself can present a security issue.

删除定义并检查条件是否处于调试模式。你不需要检查指令是否处于释放模式。

就像这样:

#if DEBUG
     Console.WriteLine("Mode=Debug"); 
#else
    Console.WriteLine("Mode=Release"); 
#endif

确保在“项目生成属性”中定义了DEBUG常量。这将启用#if DEBUG。我没有看到预定义的RELEASE常量，所以这可能意味着任何不在DEBUG块中的东西都是RELEASE模式。

bool isDebug = false;
Debug.Assert(isDebug = true); // '=', not '=='

方法Debug。Assert具有条件属性DEBUG。如果没有定义，则取消调用和isDebug = true赋值:

如果定义了符号，则包含调用;否则，调用(包括调用参数的计算)将被省略。

如果定义了DEBUG，则isDebug将被设置为true(并传递给DEBUG)。Assert，在这种情况下它什么也不做)。