Directory.GetFiles in C#: How to Retrieve Only Filenames Without Full Paths

Problem Context and Core Requirements

In C# file system operations, the Directory.GetFiles method is commonly used to retrieve all files in a specified directory. However, by default, it returns an array of filenames that include the full path, such as ["C:\dir\file1.txt", "C:\dir\file2.txt"]. In practical development, programmers often need only the filenames themselves, like ["file1.txt", "file2.txt"], to avoid the interference of path prefixes.

Core Solution: The Path.GetFileName Method

System.IO.Path.GetFileName is the standard method for addressing this issue. It takes a file path string as input and returns the filename portion of the path. Its internal implementation is based on parsing path separators, ensuring correct handling of path formats across different operating systems.

Here is a complete implementation example:

string[] files = Directory.GetFiles(dir);
foreach(string file in files)
    Console.WriteLine(Path.GetFileName(file));

In this code:

• Directory.GetFiles(dir) first obtains the full paths of all files in the directory
• Each file path is iterated, and Path.GetFileName extracts the pure filename
• The final output consists of filenames only

In-Depth Analysis of Method Principles

The working principle of Path.GetFileName is based on string processing algorithms:

1. Identify the last directory separator in the path string (\ for Windows, / for Unix systems)
2. Extract all characters after the separator as the filename
3. If no separator is present, return the original string

This design ensures cross-platform compatibility while maintaining high execution efficiency.

Analysis and Comparison of Alternative Approaches

Although the FileInfo class can be used for similar functionality:

FileInfo[] fileInfos = new DirectoryInfo(dir).GetFiles();
foreach(FileInfo fileInfo in fileInfos)
    Console.WriteLine(fileInfo.Name);

This method incurs significant performance overhead:

• FileInfo requires object instantiation and loading of complete file metadata
• Memory usage is substantially higher than simple string processing
• It is recommended only when additional file attributes like size or creation time are needed

Best Practices Recommendations

Considering performance and maintainability:

1. Prioritize the combination of Path.GetFileName and Directory.GetFiles
2. Consider the FileInfo approach only when file metadata is required
3. Handle potential exceptions, such as non-existent directories or insufficient access permissions

By adopting this optimized solution, developers can achieve full functionality while ensuring optimal performance.