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

Testing ASP Applications

Written by Eric Smith, Northstar Computer Systems LLC

One of the problems with testing ASP applications is that you have to replicate the server directory structure to perform valid tests. However, if you are working on the same server, you can't just put your files in the same places, because they'll overwrite the production copies.

You can, however, create a new web site in IIS, use the same directory structure and configuration, but use a different access port to hit the server. For instance, instead of using the default port 80, which is the live server, use an obscure port like 7654. You can then set up your development area just like the production and not have to worry about people straying in. If necessary, use IIS's security features to restrict hits from domains outside your own.

Keywords: [ Uncategorized ASP Tips ]

Publication Date: 8/9/2000