|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
Windows CE ASP supports three ASP processing directives only: Language, Codepage, and LCID. Attempts to use other identifiers result in an error.
If the ASPPARSE component is included, the <%@ %> ASP processing line behaves in the same manner as in IIS. The Web server allows these values to be set on a per-page basis.
Unlike IIS, Windows CE ASP does not check to make sure that the Preprocdirective line is the first line of the ASP page. It also does not check to see if there is only one Preprocdirective line per file. If multiple ASP processing statements are included in one file, ASP uses the values in the first directive line and treats the remaining ASP processing directives as commands in the primary scripting language. Multiple ASP processing statements in a single file cause a parse error, but it might not be immediately obvious that the problem was caused by the additional Preprocdirective lines.
It is possible to set site-wide default settings for the ASP processing directives in the registry. These values override the default ASP settings. The registry settings and ASP default settings are overridden on a requested ASP page if there is an ASP processing line on the page.
HKEY_LOCAL_MACHINE\Comm\HTTPD\ASPis the protected registry key for the default ASP settings. The following table shows the named values for the protected registry ASP configuration parameters.
|Language||A string that is equal to either "JScript" or "VBScript", depending on which language is to be used. If this value does not exist, the default is VBScript.|
|Codepage||A DWORD that is equal to the code page to use. If this value is not set and not specified as a processing directive, ASP assumes it is working with ANSI strings.|
|LCID||The LCID to use. If this value is not set and not specified as a processing directive, ASP uses the local default.|
Windows CE ASP evaluates ASP processing directives only if the ASPPARSE component has been included. However, the registry settings are read in, regardless of whether or not the ASPPARSE component has been included. In this way, it is possible to change the values (such as the scripting language) without including the ASPPARSE component. The disadvantage to not including the ASPPARSE component is that the values must be set site-wide and cannot be set on a page-by-page basis.
Last updated on Friday, April 02, 2004