ASP Directives

ASP provides directives that are not part of the scripting language you use. These directives are the output directive and the processing directives.
The ASP output directive <%= expression %> displays the value of an expression. This output directive is equivalent to using Response. Write to display information. For example, the output expression <% = sport %> sends the word climbing (the current value of the variable to the browser. The ASP processing directive <%@ keyword %> gives ASP information it needs to process an asp file. For example, the following directive sets VBScript as the Primary scripting language for the page:

< % @ LANGUAGE = VBScript %>

The processing directive must appear on the first line of an asp file. Do not
put the processing directive in a file included with the #include statement.
Your must use a space between the at sign (@) and the keyword. The processing directive has the following keywords.

LANGUAGE - Sets the Scripting language for the page

CODEPAGE page - Sets the code page(the character encoding)for the LCID Sets the locale identifier for the page.

TRANSACTION - Specifies that the page will run under a transaction context

ENABLESESSIONSTATE - Specifies whether an ASP Page uses session state.

You can include more than one keyword in a single directive; key word / value pairs must be separated by a space. Do not put spaces around the equal sign (=). The following example sets both the scripting language and the code page:

<%@ LANGUAGE = Jscript CODEPAGE = 932 %>

Domain Name Search