Beginning Active Server Pages


Developers who make regular use of the VB debugging tools will be in for a shock - there are virtually none for ASP! On your local server, you usually receive a 505 error when there is a scripting error, along with the error description and line number that it occured on.... and that is just about it. If you have a custom 505 error page, you won't even be able to get that.

Note that if you have started sending information to the browser (after a Response.Flush call, or with buffering disabled - see performance section), then you an error will be outputted with your HTML. However, if the error occured in VB code, which is within a table, then you may well not see it... you will need to go to View | Page Source in order to find out what went wrong!

At the moment, Visual InterDev provides the best debugging tools, which are remenicsent of VB. Otherwise, you will simply have to revert to putting Response.Write "doing something..." to check that things are running as you expect. As always, use of the Option Explicit statement also prevents you getting into a mess with variable names. Other than that, you are on your own.... sorry!

You might also like...


About the author

James Crowley

James Crowley United Kingdom

James first started this website when learning Visual Basic back in 1999 whilst studying his GCSEs. The site grew steadily over the years while being run as a hobby - to a regular monthly audien...

Interested in writing for us? Find out more.


Why not write for us? Or you could submit an event or a user group in your area. Alternatively just tell us what you think!

Our tools

We've got automatic conversion tools to convert C# to VB.NET, VB.NET to C#. Also you can compress javascript and compress css and generate sql connection strings.

“Anyone who considers arithmetic methods of producing random digits is, of course, in a state of sin.” - John von Neumann