Important:
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.
A version of this page is also available for
4/8/2010

The Serverobject provides access to methods and properties on the server. Most of these methods and properties serve as utility functions. The following table shows the supported server methods.

Server method Windows Embedded CE implementation

ScriptTimeout

Not supported.

CreateObject

Not supported.

Execute

Not supported.

GetLastError

Not supported.

HTMLEncode

Not supported.

MapPath

Fully supported.

Transfer

Not supported.

URLEncode

Fully supported.

To create a COM object on Windows Embedded CE–based ASP, use the scripting language support for creating COM objects, instead of the Server.CreateObjectmethod, as you would using IIS-based ASP.

In JScript, the following code would create the object of type class.name.

Copy Code
<% var newObject = new ActiveXObject("class.name") %>

To perform the same operation using VBScript, use the following code.

Copy Code
<%
	dim newObject
	set newObject = CreateObject("class.name")
%>

There is no explicit need to delete COM objects that are created on ASP pages. This is unlike needs associated with using JScript or VBScript. ASP automatically deletes all COM objects that are created on ASP pages. For more information on ASP and the caching of DLLs, see Initial Settings.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.