I have some code which is littered with debug expressions similar to:
System.Diagnostics.Debug.WriteLine(System.BitConverter.ToString(data.Take(32).ToArray()));
What can I do to prevent the Release version evaluating System.BitConverter.ToString(data.Take(32).ToArray())
?
I have added my own debug class that allows me to control calls to WriteLine()
based on the level of reporting I want but both methods evaluate the Linq and string conversion even in Release mode (don't they)?
---ADDED LATER---
As I said above there are many of these lines in the code and I don't particularly want to #if DEBUG
them all out.
What I want is to know how to avoid evaluating the Linq and the BitConverter, which I assume will be a performance hit, in Release mode.
You do not have to do anything! The evaluation of the parameters passed to a method that is removed because of the
ConditionalAttribute
is suppressed already.See the section The Conditional attribute in the C# Language Specification for authoritative documentation. Quote:
To see that the method actually carries the
ConditionalAttribute
, seeDebug.WriteLine(string)
documentation.#if DEBUG
should solve it to you:More examples here.
The answers and comments prompted me to test my supposition that the conversion is evaluated in Release mode.
In Release mode I get the output:
So the Debug line isn't being evaluated at-all in Release mode and I don't need to do any more than use the Debug output and/or add
[Conditional("DEBUG")]
to my own debug routines (which is already an attribute of the library Debug code).[Conditional("DEBUG")]
- although an attribute of the called function, prevents the function call which prevents the evaluation of parameters to it. It acts in a way very similar to#if DEBUG