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

Buffering and Debug Statements

Written by Eric Smith, Northstar Computer Systems LLC

One of the things I do frequently while I'm programming is dump values out to indicate where I'm at as the page executes. However, if an error occurs, you may or may not see the lines you created with Response.Write. The property that controls this is the Response.Buffer property. If buffering is turned on (which it is by default in Windows 2000 and later), you will see the error message but no other text. If buffering is turned off (as in Windows NT 4.0), you'll see any text generated up to the point that the error occurred. If you're building your pages and anticipate errors, just turn buffering off, either at a site-wide level or on a per-page basis with this code:
Response.Buffer = False

Keywords: [ ASP Built-in Objects | ASP Debugging ]

Publication Date: 7/1/2000, Last Update: 2/13/2010