Additionally, to save resources, you can use compiler directives so as to
only include Debug commands during the development phase.

Doing something like: 

#Const DEBUGGING=True

#If DEBUGGING = True
Debug.WriteLine()
#End If

This is for VB.NET. Don't know if you can do the same for c#. You probably
can. When you want to get rid of them all, just set DEBUGGING to false and
they will know longer be including in the MSIL on compilation. 

-----Original Message-----
From: Wim Hollebrandse [mailto:wim@w...]
Sent: 13 January 2003 16:12
To: ASPX_Professional
Subject: [aspx_professional] Re: Debugging in VS.Net


Use Debug.Write or Debug.WriteLine.

In order to use these, you need to import the System.Diagnostics namespace.

Hope this helps,
Wim Hollebrandse
http://www.wimdows.net


----- Original Message -----
From: <artimahendra@s...>
To: "ASPX_Professional" <aspx_professional@p...>
Sent: Monday, January 13, 2003 10:51 AM
Subject: [aspx_professional] Re: Debugging in VS.Net


> > Hi ,
> Whats the equivalent of debug.print statement which was there in VS 6.0 in
> visual studio.Net?
>