|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.|
The Windows CE implementation of ASP supports a subset of the features that are supported by the IIS implementation. This section lists the features that are not supported by Windows CE ASP.
No State Maintained Between Requests
This is the greatest difference between the IIS and Windows CE implementations of ASP. Windows 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 state 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 by using the Response.Cookiesmethod and retrieving them by using the Request.Cookiesmethod. This scheme assumes that the client browser has cookie support enabled.
No <OBJECT> Tag support
The <OBJECT> tag and properties are treated as plain text by Windows CE ASP. Interpretation of the <OBJECT> tag by the client browser is browser-specific. For more information, see Server Object Implementation.
No Transaction Support
None of the methods or properties that are associated with transactions is supported on Windows CE ASP. Tags and commands that are used by ASP on IIS to support transactions are ignored by Windows CE ASP and treated as plain text. How the client browser interprets these values is browser-specific.
No Server-side Scriptlets
There is no support for server-side scriptlets in Windows CE ASP. The <SCRIPTLET> and related tags are ignored by Windows CE ASP and treated as plain text. How the client browser interprets the <SCRIPTLET> tag is browser-specific.
No 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 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.
No Global.asa File
Windows CE 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.
No Automatic Initialization or Termination Functions
Script procedures may be named Application_OnStart, Application_OnEnd, Session_OnStart, or Session_OnEnd, although Windows CE ASP does not treat them differently from any other user-created procedures. Windows CE ASP does not call script procedures automatically on application or session initialization or termination, as is the case on IIS ASP.
No Metabase Support
The Windows CE Web server does not provide metabase support. If a script contains a property that can be set in the IIS metabase, but is not explicitly listed as supported in this Windows CE Web server document, it is not supported for use with the Windows CE Web server. For example, scripts containing ScriptMapstatements may operate correctly with IIS, but will fail with the Windows CE Web server.
Last updated on Friday, April 02, 2004