NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Adding Permanent Debugging Code

Written by Eric Smith, Northstar Computer Systems LLC

If you've built a lot of complex ASP code, you've probably added lots of Response.Write statements to print out values during the run of a page. As I hate having to re-enter all that data any time I have to debug the application, I created a handy function that is added "permanently" to the code. Based on a constant value defined in a server-side include file, the function will add comments to the output HTML with values that I need to see along the way. Here's the code:
Sub WriteDebugValue(strText)
   If DEBUG Then
      Response.Write "<!-- " & strText & " -->" & vbCrLf
   End If
End Sub
The DEBUG constant is a simple constant defined like this:
Const DEBUG = True
If you want to disable the debugging code, just set the value to False.

Keywords: [ ASP Debugging ]

Publication Date: 1/1/2000, Last Update: 2/12/2010