Home/ Questions/Q 33147
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T13:52:29+00:00

For years I have been using the DEBUG compiler constant in VB.NET to write

  • 0

For years I have been using the DEBUG compiler constant in VB.NET to write messages to the console. I’ve also been using System.Diagnostics.Debug.Write in similar fashion. It was always my understanding that when RELEASE was used as the build option, that all of these statements were left out by the compiler, freeing your production code of the overhead of debug statements. Recently when working with Silverlight 2 Beta 2, I noticed that Visual Studio actually attached to a RELEASE build that I was running off of a public website and displayed DEBUG statements which I assumed weren’t even compiled! Now, my first inclination is to assume that that there is something wrong with my environment, but I also want to ask anyone with deep knowledge on System.Diagnostics.Debug and the DEBUG build option in general what I may be misunderstanding here.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. The preferred method is to actually use the conditional attribute to wrap your debug calls, not use the compiler directives. #ifs can get tricky and can lead to weird build problems.

    An example of using a conditional attribute is as follows (in C#, but works in VB.NET too):

    [ Conditional('Debug') ] private void WriteDebug(string debugString) {   // do stuff }

    When you compile without the DEBUG flag set, any call to WriteDebug will be removed as was assumed was happening with Debug.Write().

    • 0