#If DEBUG is ignored (VB.net or C#)

前端 未结 8 1044
青春惊慌失措
青春惊慌失措 2021-02-05 13:33

I have several of these in my code which have been working fine so far:

#If DEBUG Then    
   ... some code here       
#End If     

Now, i am

相关标签:
8条回答
  • 2021-02-05 13:48

    C# Project ( Visual Studio )

    1. go to: Project Properties -> Build(tab)
    2. Select Configuration: Release
    3. Uncheck "Define DEBUG constant"

    4. Now select Configuration: Debug

    5. Check "Define DEBUG constant"

    6. In your code, you can now type the following ( DEBUG with uppercase )

    #IF DEBUG
    
    // Debugging code goes here
    
    #ENDIF
    
    0 讨论(0)
  • 2021-02-05 13:51

    Also remember #if DEBUG must be in uppercase. e.g. #if debug won't work.

    0 讨论(0)
  • 2021-02-05 13:52

    undefine DEBUG and that will not execute that portion.

    0 讨论(0)
  • 2021-02-05 14:01

    Had a similar problem where "DEBUG" was never true. Tried by doing an uncheck and check of the "Define DEBUG constant" checkbox and rebuilding everytime but that did not work.

    My solution was to define "DEBUG" manually in the "Conditional compilation symbols" textbox for the Debug configuration. When rebuilding, Visual Studio 2019 automatically removed the DEBUG symbol from the textbox (because this indeed should not be there) and from then on it worked again. When i switched from Debug to Release the correct lines got greyed out. This seems to be a possible bug in VS 2019 (16.4.5)?

    0 讨论(0)
  • 2021-02-05 14:07

    Firstly, make sure you understand the difference between how you're running the code and how you're building it. Too many people equate "launching in a debugger" with "the debug version" and "launching not in a debugger" with "the release version". They're completely orthogonal - you can launch a release build in a debugger (typically with less information available) and you can launch a debug build not in a debugger. Apologies if you were already aware of this.

    Now, assuming you really have changed the project configuration you're building to Release, you need to check the project properties for that specific configuration. I don't know what it looks like in VB, but in C# in the project properties, in the build tab, there will be a list of defined symbols - that is what affects whether #if DEBUG code is built or not. Perhaps someone has copied over the project configuration from Debug into Release?

    EDIT: One way to check this at build time is:

    #if DEBUG
    #error This shouldn't happen
    #endif
    

    In a release build, that should build without error. In debug, it won't.

    EDIT: Another option is that your overall solution configuration is now referring to the wrong project configuration types. I can't remember the exact menu name, but if you look around Project for Configuration Manager, you should be able to bring up a grid mapping "Project" and "Solution Configuration" to the project configuration to build.

    0 讨论(0)
  • 2021-02-05 14:13

    Under Project Properties / Compile / Advanced Compile Options there is a checkbox called "Define Debug Constant" that sets this.

    Check out: http://www.experts-exchange.com/Programming/Languages/Visual_Basic/Q_24658238.html

    EDIT: Try this initializing with this:

    #If CONFIG = "Debug" Then
    #CONST DEBUG = true
    
    #if CONFIG = "Release" Then
    #CONST DEBUG = false
    
    0 讨论(0)
提交回复
热议问题