Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is different between using #if (DEBUG) and System.Diagnostics.Debugger.IsAttached in visual studio? Are there cases of the DEBUG flag being set, but no debugger attached, or cases when a debugger could be attached when the DEBUG flag is not set?
#if DEBUGensures the code is not included in the assembly at all in release builds. Also, code included by#if DEBUGruns all the time in a debug build – not just when running under a debugger.Debugger.IsAttachedmeans the code is included for both debug and release builds. And a debugger can be attached to release builds too.It’s common to use both together.
#if DEBUGis usually used for things like logging, or to reduce exception handling in internal test builds.Debugger.IsAttachedtends to just be used to decide whether to swallow exceptions or show them to a programmer – more of a programmer aid than anything else.