The success of an "Active Server Page (ASP)" application often depends on the trade-offs on architecture and design. Given the wide range of ASP technology and the inherent complexity of current applications, this trade-off is very difficult. In this article, I will provide you with some specific guidelines to help you successfully develop ASP-based applications.
I have put the guidelines into a set of development principles. When evaluating solutions and technologies, the following principles can be applied to help you make decisions. The following principles are my long-term experience gained from successful development models.
Establishing naming conventions and standardizing the directory structure can help you greatly improve the readability and maintainability of your ASP applications. Although there are currently no formal standards for ASP applications, many developers have established some common ways. Here, I will share with you some more general ways.
Because ASP technology relies on script engines to work, and scripts have a nature of being not strict in type, the naming conventions are also vague. In languages with very strict types, variables will be declared according to their actual type. When using ASP technology, variables are usually declared in ASP code in the way they process variables, rather than their actual data type. For example, when using "Visual Basic(R) Scripting Edition (VBScript)", although all VBScript variables are Variant, you declare the success flag as bSuccess (b for boolean) instead of vSuccess (v for Variant).
The following table is some common naming conventions.
Variable prefix: