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. |
This function gets the path to the directory designated for temporary files on a remote Windows Embedded CE–based device.
Syntax
DWORD CeGetTempPath( DWORD nBufferLength, LPWSTR lpBuffer ); |
Parameters
- nBufferLength
-
[in] Size of lpBufferin characters.
- lpBuffer
-
[out] Reference to a wide string buffer that receives the null-terminated wide string specifying the temporary path. The returned string ends with a backslash (/).
Return Value
The return value is the length, in wide characters, of the string copied to lpBuffer, not including the terminating null character. If the return value is greater than nBufferLength, the return value is the size, in characters, of the buffer required to hold the path.
If CeGetTempPathfails, the return value is 0. To determine whether a function failed because of RAPI errors, call CeRapiGetError. To determine whether a function failed because of non-RAPI errors, call CeGetLastError.
Remarks
The CeGetTempPathfunction gets the temporary file path as follows:
- The path specified by the TMP environment variable.
- The path specified by the TEMP environment variable, if TMP is
not defined.
- The current directory, if both TMP and TEMP are not defined.
Requirements
Header | rapi.h |
Library | rapi.lib |
Windows Embedded CE | Windows CE 3.0 and later |
Windows Mobile | Pocket PC 2000 and later, Smartphone 2002 and later |
See Also
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.