Partager via


MyFSD_MoveFileW (Windows CE 5.0)

Send Feedback

This function renames an existing file or a directory, including all its children, that resides in an installable file system. The application does not call this function directly. Instead, use the corresponding standard Win32 function MoveFile. The FSD Manager determines the file system type and calls the MyFSD_MoveFileW implementation of the function.

BOOLMyFSD_MoveFileW( PVOLUMEpVolume,PCWSTRpwsOldFileName,PCWSTRpwsNewFileName);

Parameters

  • pVolume
    [in] Pointer to the value that an FSD defines in its DLL and passes to the FSDMGR_RegisterVolume function when registering the volume. The definition of pVolume can point to private structures.
  • pwsOldFileName
    [in] Pointer to a null-terminated string that names an existing file or directory.
  • pwsNewFileName
    [in] Pointer to a null-terminated string that specifies the new name of a file or directory. The new name must not already exist. A new file may be on a different file system or drive. A new directory must be on the same drive.

Return Values

Nonzero indicates success. Zero indicates failure. To get extended error information, call GetLastError.

Remarks

An FSD exports this function, if it wants to support the MoveFile function. All FSD functions can be called on re-entry; therefore, FSD developers must take this into account when developing an FSD.

The Fsdmgr component is a DLL that manages all OS interaction with installable files systems. Each installable file system requires an FSD, which is a DLL that exports an API needed to support an installable file system. The name of the DLL and the names of the functions it exports start with the name of the associated installable file system. For example, if the name of file system is MyFSD, then its DLL is MyFSD.dll and its exported functions are prefaced with MyFSD_*.

Fsdmgr provides services to FSDs. The FSDMGR_RegisterVolume, FSDMGR_CreateFileHandle, and FSDMGR_CreateSearchHandle functions record a DWORD of volume-specific data an FSD needs to keep associated with volume. This volume-specific data is passed as the first parameter of these three functions.

Applications that access an installable file system use standard Win32 functions. For example, when an application wants to create a folder on a device that contains an installable file system, it calls CreateDirectory. Fsdmgr recognizes that the path is to a device containing an installable file system and calls the appropriate function, which in the case of the FAT file system is FATFSD_CreateDirectoryW. That is, the application calls CreateDirectory, causing Fsdmgr to call FATFSD_CreateDirectoryW.

The MoveFile function will move, or rename, either a file or a directory, including all its children, either in the same directory or across directories. The one caveat is that the MoveFile function will fail on directory moves when the destination is on a different volume.

Requirements

OS Versions: Windows CE 2.10 and later.
Header: Fsdmgr.h.
Link Library: Fsdmgr.lib.

See Also

CreateDirectory | FSDMGR_CreateFileHandle | FSDMGR_CreateSearchHandle | FSDMGR_RegisterVolume | MoveFile

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.