如何在Azure Storage中重命名CloudFile/CloudFileDirectory对象（非Blob）

Hey there! I totally get your frustration—this feels like it should be a straightforward task, but Azure File Storage doesn’t offer a direct "rename" method for CloudFile or CloudFileDirectory objects. The good news is you don’t have to resort to copying files locally and deleting the originals. Instead, we can use server-side move/copy operations (which act as renames within the same file share) that are efficient, bandwidth-friendly, and handled entirely within Azure’s infrastructure.

Renaming a CloudFile #

For individual files, the server-side copy operation is your best bet. When targeting a new name in the same share, Azure treats this as an internal rename—no data gets transferred to your application. Here’s how to implement it with the legacy Microsoft.Azure.Storage.File library:

using Microsoft.Azure.Storage;
using Microsoft.Azure.Storage.File;
using System.Threading.Tasks;

public async Task RenameCloudFileAsync()
{
    string connectionString = "your-storage-connection-string";
    string shareName = "your-file-share";
    string oldFileName = "old-report.pdf";
    string newFileName = "2024-q3-report.pdf";

    // Initialize storage client and share reference
    CloudStorageAccount storageAccount = CloudStorageAccount.Parse(connectionString);
    CloudFileClient fileClient = storageAccount.CreateCloudFileClient();
    CloudFileShare share = fileClient.GetShareReference(shareName);
    
    // Get reference to the original file
    CloudFile originalFile = share.GetRootDirectoryReference().GetFileReference(oldFileName);
    
    // Validate original file exists
    if (!await originalFile.ExistsAsync())
    {
        throw new FileNotFoundException("Original file not found.", oldFileName);
    }

    // Get reference to the target (renamed) file
    CloudFile targetFile = share.GetRootDirectoryReference().GetFileReference(newFileName);
    
    // Start server-side copy (fast, no data leaves Azure)
    await originalFile.StartCopyAsync(targetFile);
    
    // Wait for copy to complete before deleting original
    while ((await originalFile.CopyStateAsync()).Status != CopyStatus.Success)
    {
        await Task.Delay(1000);
    }
    
    // Delete the original file to complete the rename
    await originalFile.DeleteAsync();
}

Important: This server-side operation avoids downloading/uploading large files to your local machine, making it infinitely more efficient than manual copy-delete for big files.

Renaming a CloudFileDirectory #

For directories, the process mirrors the file workflow—we use server-side copy to duplicate the entire directory structure to a new name, then delete the original. This handles all nested files and subdirectories automatically:

public async Task RenameCloudFileDirectoryAsync()
{
    string connectionString = "your-storage-connection-string";
    string shareName = "your-file-share";
    string oldDirName = "project-archives-2023";
    string newDirName = "project-archives-2023-archived";

    CloudStorageAccount storageAccount = CloudStorageAccount.Parse(connectionString);
    CloudFileClient fileClient = storageAccount.CreateCloudFileClient();
    CloudFileShare share = fileClient.GetShareReference(shareName);
    
    CloudFileDirectory originalDir = share.GetRootDirectoryReference().GetDirectoryReference(oldDirName);
    if (!await originalDir.ExistsAsync())
    {
        throw new DirectoryNotFoundException("Original directory not found.", oldDirName);
    }

    CloudFileDirectory targetDir = share.GetRootDirectoryReference().GetDirectoryReference(newDirName);
    
    // Start server-side copy of the entire directory (recursive)
    await originalDir.StartCopyAsync(targetDir);
    
    // Wait for copy completion
    while ((await originalDir.CopyStateAsync()).Status != CopyStatus.Success)
    {
        await Task.Delay(1000);
    }
    
    // Delete the original directory
    await originalDir.DeleteAsync();
}

Note: While directory copies aren’t atomic, Azure manages the process server-side, so the risk of partial copies is minimal.

Key Tips #

• Same Share Constraint: These methods only work within the same file share. Cross-share moves do require copy-delete, but that’s an Azure limitation, not a code issue.
• Modern SDK Alternative: If you can switch to the newer Azure.Storage.Files.Shares library, use ShareFileClient.MoveToAsync() and ShareDirectoryClient.MoveToAsync()—these methods directly handle renaming without needing manual deletion of the original.

内容的提问来源于stack exchange，提问作者IMollov