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

This structure describes the changes found by the CeGetFileNotificationInfofunction.

Syntax 

typedef struct _FILE_NOTIFY_INFORMATION {
  DWORD 
NextEntryOffset; 
  DWORD 
Action; 
  DWORD 
FileNameLength; 
  WCHAR 
FileName[1]; 
} FILE_NOTIFY_INFORMATION, *PFILE_NOTIFY_INFORMATION;

Members

NextEntryOffset

Number of bytes that must be skipped to get the next record. A value of zero indicates that this is the last record.

Action

Type of change that occurred. The following table shows possible values.

Value Description

FILE_ACTION_ADDED

The file was added to the directory.

FILE_ACTION_MODIFIED

The file was modified. This can be a change in the time stamp or attributes.

FILE_ACTION_REMOVED

The file was removed from the directory.

FILE_ACTION_RENAMED_NEW_NAME

The file was renamed, and this value is the new name.

FILE_ACTION_RENAMED_OLD_NAME

The file was renamed, and this value is the old name.
FileNameLength

Length of the file name portion of the record, in bytes. The length does not include the terminating NULL character.

FileName

File name, relative to the directory handle. The file name is in Unicode format and is not null-terminated.

Requirements

Header winnt.h
Windows Embedded CE Windows CE 1.01 and later
Windows Mobile Windows Mobile Version 5.0 and later

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.