ASP Functionality in Windows Embedded CE (Windows Embedded CE 6.0)

Article
01/05/2012

1/6/2010

The Windows Embedded CE implementation of ASP supports a subset of the functionality that is supported by the IIS implementation of ASP. The following list shows the functionality that is not supported by Windows Embedded CE–based ASP:

State Maintained Between Requests

This is the greatest difference between the IIS and Windows Embedded CE implementations of ASP. Windows Embedded CE does not provide support for the Session or Application objects and does not send the Session-ID cookie that is used on IIS. Therefore, there is no automatic technique for maintaining states between requests or sessions.

The script writer must maintain information between requests and sessions. A script writer can do this by sending cookies to the client browser. This scheme assumes that the client browser has cookie support enabled.

Tag support

Windows Embedded CE–based ASP treats the <OBJECT> tag and properties as plain text. Interpretation of the <OBJECT> tag by the client browser is browser-specific. For more information, see Server Object Implementation.

Transaction Support

None of the methods or properties that are associated with transactions is supported on Windows Embedded CE–based ASP. Tags and commands that are used by ASP on IIS to support transactions are ignored by Windows Embedded CE–based ASP and treated as plain text. How the client browser interprets these values is browser-specific.

Server-Side Scriptlets

There is no support for server-side scriptlets in Windows Embedded CE–based ASP. The <SCRIPTLET> tag and related tags are ignored by Windows Embedded CE–based ASP and treated as plain text. How the client browser interprets the <SCRIPTLET> tag is browser-specific.

Additional Server-Side Scripting Options

On IIS, it is possible to specify options such as <SCRIPT LANGUAGE = JSCRIPT RUNAT = SERVER>, in which case the code between the <SCRIPT> and </SCRIPT> tags is executed on the server in the specified language, instead of on the client computer.

Windows Embedded CE ignores the RUNAT option of <SCRIPT> tags and sends the script to the client browser. How the client browser interprets the RUNAT option is browser-specific.

Global.asa File

Windows Embedded CE–based ASP does not search automatically for a file that is named Global.asa to obtain global settings. Initial settings or commonly used routines may be included by using header files.

Automatic Initialization or Termination Functions

Script procedures may be named Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd, although Windows Embedded CE–based ASP does not treat them differently from any other user-created procedures. Windows Embedded CE–based ASP does not call script procedures automatically on application or session initialization or on termination, as is the case with IIS-based ASP.

Metabase Support

The Web Server does not provide metabase support. If a script contains a property that can be set in the IIS metabase, but that is not explicitly listed as supported in this Web Server document, it is not supported for use with the Web Server. For example, scripts containing ScriptMap statements may operate correctly with IIS, but they will fail with the Web Server.