MyFSD_DeleteAndRenameFileW
This function deletes the source file, pwsOldFileName, after it copies the content of the source file to the destination file, pwsNewFileName, in an installable file system. The application does not call this function directly. Instead, use the corresponding standard Win32 function DeleteAndRenameFile. The file system driver (FSD) Manager determines the file system type and calls the MyFSD_DeleteAndRenameFileW implementation of the function.
BOOL MyFSD_DeleteAndRenameFileW(
PVOLUME pVolume
PCWSTR pwsOldFileName,
PCWSTR pwsNewFileName);
Parameters
- pVolume
Pointer to the value that the file system driver (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
Pointer to the string that contains the path of the source file. This parameter cannot be NULL. - pwsNewFileName
Pointer to the string that contains the path of the destination file. This parameter cannot be NULL.
Return Values
TRUE indicates success. FALSE indicates failure. Call GetLastError to get detailed error messages.
Remarks
An FSD exports this function if it wants to support the DeleteAndRenameFile function. All FSD functions can be called reentryly, therefore, FSD developers must take this into account when developing an FSD.
The Fsdmgr component is a dynamic-link library (DLL) that manages all operating system 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 for the FSD 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 service functions to FSDs. The FSDMGR_RegisterVolume, FSDMGR_CreateFileHandle, and FSDMGR_CreateSearchHandle functions record a DWORD of volume-specific data the 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 MyFSD file system is MyFSD_CreateDirectoryW. That is, the application calls CreateDirectory, causing Fsdmgr to call **MyFSD_CreateDirectoryW.
Requirements
| Runs on | Versions | Defined in | Include | Link to |
|---|---|---|---|---|
| Windows CE OS | 2.10 and later | Fsdmgr.h |
Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
See Also
CreateDirectory, DeleteAndRenameFile, FSDMGR_CreateFileHandle, FSDMGR_CreateSearchHandle, FSDMGR_RegisterVolume, GetLastError, MyFSD_CreateDirectoryW
Last updated on Tuesday, July 13, 2004
© 1992-2000 Microsoft Corporation. All rights reserved.