默认情况下，如果项目在调试模式下编译，Visual Studio定义DEBUG，如果项目在发布模式下编译，则不定义DEBUG。默认情况下，RELEASE模式中没有定义RELEASE。可以这样说:

#if DEBUG
  // debug stuff goes here
#else
  // release stuff goes here
#endif

如果你只想在发布模式下做某事:

#if !DEBUG
  // release...
#endif

此外，值得指出的是，您可以在返回void的方法上使用[Conditional("DEBUG")]属性，以便仅在定义了某个符号时执行它们。如果符号没有定义，编译器将删除对这些方法的所有调用:

[Conditional("DEBUG")]
void PrintLog() {
    Console.WriteLine("Debug info");
}

void Test() {
    PrintLog();
}

我不是#if之类的东西的超级粉丝，特别是如果你把它散布在你的代码库中，因为如果你不小心，它会给你带来调试构建通过但发布构建失败的问题。

下面是我想出的(灵感来自c#中的#ifdef):

public interface IDebuggingService
{
    bool RunningInDebugMode();
}

public class DebuggingService : IDebuggingService
{
    private bool debugging;

    public bool RunningInDebugMode()
    {
        //#if DEBUG
        //return true;
        //#else
        //return false;
        //#endif
        WellAreWe();
        return debugging;
    }

    [Conditional("DEBUG")]
    private void WellAreWe()
    {
        debugging = true;
    }
}

Since the purpose of these COMPILER directives are to tell the compiler NOT to include code, debug code,beta code, or perhaps code that is needed by all of your end users, except say those the advertising department, i.e. #Define AdDept you want to be able include or remove them based on your needs. Without having to change your source code if for example a non AdDept merges into the AdDept. Then all that needs to be done is to include the #AdDept directive in the compiler options properties page of an existing version of the program and do a compile and wa la! the merged program's code springs alive!.

对于还没有准备好进入黄金时段的新流程，或者在发布之前不能在代码中活动的新流程，您可能还想使用声明式。

总之，我就是这么做的。

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.

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

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

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

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

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