How can I test if code is running in debug mode?

[Wysiwyg]

Is there any way besides adding a specific debug command line argument for
the project to tell if an application is running in debug mode?

Thanks!
Bill

[John Timney \(ASP.NET MVP\)]

You can test against conditional directives to get your code to tell you
what mode its in

private void Test()
{
#if DEBUG
Console.WriteLi ne("In Debug..");
#endif
}

See here:
http://msdn.microsoft.com/library/de...ml/vclrfif.asp

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"Wysiwyg" <wy*****@xmissi onNSPAM.com> wrote in message
news:d5******** **@news.xmissio n.com...

Is there any way besides adding a specific debug command line argument for
the project to tell if an application is running in debug mode?

Thanks!
Bill

[ESPNSTI]

I think you can also use:

public void Foo1()
{
If (Debugger.IsAtt ached)
Foo2();
}

or

[Conditional("DE BUG")]
public void Foo1()
{
Foo2();
}

[Bruce Wood]

Be careful! System.Diagnost ics.Debugger.Is Attached and #if DEBUG (or
the equivalent [Conditional("DE BUG")] ) have different effects! It
depends upon what you want!

#if DEBUG

and

[Conditional("DE BUG")]

tell the compiler to include the code (or the method) only for a _Debug
build_. So, if you compile the code under the Debug configuration (see
Configuration Manager under the Build menu), then the code will be
included. If you compile the code under the Release configuration then
the code will not be included.

It does not matter whether you run the Debug configuration under
debugger control, or run it from the command line. Code included using
#if DEBUG will exist and execute no matter how the application is run.
Similarly, the Release assembly will not include the code, so no matter
how it is run the code will never execute (because it's not compiled
in).

System.Diagnost ics.Debugger.Is Attached produces a different effect: the
code is always compiled in, in all configurations. However, it runs
_only if_ the application is running under control of the debugger.
Even if you compile the Debug configuration, if you run it from the
command line (with no debugger), code within an

if (System.Diagnos tics.Debugger.I sAttached)
{
... code here ...
}

will not execute, because the executable is not running under debugger
control.

[Wysiwyg]

Thanks to both of you!

Bill

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:%2******** *******@TK2MSFT NGP15.phx.gbl.. .

You can test against conditional directives to get your code to tell you
what mode its in

private void Test()
{
#if DEBUG
Console.WriteLi ne("In Debug..");
#endif
}

See here:
http://msdn.microsoft.com/library/de...ml/vclrfif.asp
--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director
"ESPNSTI" <ES*********@Ho tmail.com> wrote in message
news:eE******** ******@TK2MSFTN GP09.phx.gbl... I think you can also use:

public void Foo1()
{
If (Debugger.IsAtt ached)
Foo2();
}

or

[Conditional("DE BUG")]
public void Foo1()
{
Foo2();
}

[Wysiwyg]

Bruce,

Thanks for the clarification.

"Bruce Wood" <br*******@cana da.com> wrote in message
news:11******** *************@o 13g2000cwo.goog legroups.com...

Be careful! System.Diagnost ics.Debugger.Is Attached and #if DEBUG (or
the equivalent [Conditional("DE BUG")] ) have different effects! It
depends upon what you want!

#if DEBUG

and

[Conditional("DE BUG")]

tell the compiler to include the code (or the method) only for a _Debug
build_. So, if you compile the code under the Debug configuration (see
Configuration Manager under the Build menu), then the code will be
included. If you compile the code under the Release configuration then
the code will not be included.

It does not matter whether you run the Debug configuration under
debugger control, or run it from the command line. Code included using
#if DEBUG will exist and execute no matter how the application is run.
Similarly, the Release assembly will not include the code, so no matter
how it is run the code will never execute (because it's not compiled
in).

System.Diagnost ics.Debugger.Is Attached produces a different effect: the
code is always compiled in, in all configurations. However, it runs
_only if_ the application is running under control of the debugger.
Even if you compile the Debug configuration, if you run it from the
command line (with no debugger), code within an

if (System.Diagnos tics.Debugger.I sAttached)
{
... code here ...
}

will not execute, because the executable is not running under debugger
control.

[Daniel Jin]

one correction, methods marked with ConditionalAttr ibute are always included
in the compiled dll. only the calling code is omitted depending on the
symbol defined. otherwise, methods like Debug.XXX and Trace.XXX would've
never made it into the BCL.

"Bruce Wood" wrote:

Be careful! System.Diagnost ics.Debugger.Is Attached and #if DEBUG (or
the equivalent [Conditional("DE BUG")] ) have different effects! It
depends upon what you want!

#if DEBUG

and

[Conditional("DE BUG")]

tell the compiler to include the code (or the method) only for a _Debug
build_. So, if you compile the code under the Debug configuration (see
Configuration Manager under the Build menu), then the code will be
included. If you compile the code under the Release configuration then
the code will not be included.

It does not matter whether you run the Debug configuration under
debugger control, or run it from the command line. Code included using
#if DEBUG will exist and execute no matter how the application is run.
Similarly, the Release assembly will not include the code, so no matter
how it is run the code will never execute (because it's not compiled
in).

System.Diagnost ics.Debugger.Is Attached produces a different effect: the
code is always compiled in, in all configurations. However, it runs
_only if_ the application is running under control of the debugger.
Even if you compile the Debug configuration, if you run it from the
command line (with no debugger), code within an

if (System.Diagnos tics.Debugger.I sAttached)
{
... code here ...
}

will not execute, because the executable is not running under debugger
control.

[Where's the Debugger?]

Search for: Ollydbg.exe An excellent debugger of which version 10 or later
has been posted. From the "readme"..."Oll yDbg 1.10 is a 32-bit
assembler-level analyzing debugger for
Microsoft(R) Windows(R) with intuitive interface."
"http://home.t-online.de/home/Ollydbg"
"Wysiwyg" wrote:

Is there any way besides adding a specific debug command line argument for
the project to tell if an application is running in debug mode?

Thanks!
Bill