Introduction

In .NET, OpenFileDialog usually gives you the full selected path through FileName. Once you have that string, the right way to extract the directory, file name, extension, or base name is to use System.IO.Path, not manual string slicing.

That matters because path strings can contain different separators, UNC shares, extensions, and edge cases that string splitting handles poorly. Path exists specifically to solve that parsing reliably.

Start With FileName

For both WinForms and WPF, the full selected path is available as FileName after the dialog succeeds.

WinForms example:

1using System.IO;
2using System.Windows.Forms;
3
4var dialog = new OpenFileDialog
5{
6    Filter = "Text files (*.txt)|*.txt|All files (*.*)|*.*"
7};
8
9if (dialog.ShowDialog() == DialogResult.OK)
10{
11    string fullPath = dialog.FileName;
12    string directory = Path.GetDirectoryName(fullPath)!;
13    string fileName = Path.GetFileName(fullPath);
14    string nameWithoutExtension = Path.GetFileNameWithoutExtension(fullPath);
15    string extension = Path.GetExtension(fullPath);
16}

That is the normal pattern: get the full path from the dialog, then ask Path for the part you need.

Use the Right Path Method for the Job

The most common methods are:

• 'Path.GetDirectoryName(path) for the folder'
• 'Path.GetFileName(path) for the file name with extension'
• 'Path.GetFileNameWithoutExtension(path) for the base name'
• 'Path.GetExtension(path) for the extension'

Example:

1string path = @"C:\Projects\Reports\sales.csv";
2
3Console.WriteLine(Path.GetDirectoryName(path));            // C:\Projects\Reports
4Console.WriteLine(Path.GetFileName(path));                 // sales.csv
5Console.WriteLine(Path.GetFileNameWithoutExtension(path)); // sales
6Console.WriteLine(Path.GetExtension(path));                // .csv

This is much safer than splitting on backslashes or dots by hand.

WPF Uses a Different Dialog Type, Same Path Logic

In WPF, the dialog type is different, but FileName and Path usage are still familiar:

1using Microsoft.Win32;
2using System.IO;
3
4var dialog = new OpenFileDialog
5{
6    Filter = "Images (*.png;*.jpg)|*.png;*.jpg|All files (*.*)|*.*"
7};
8
9if (dialog.ShowDialog() == true)
10{
11    string directory = Path.GetDirectoryName(dialog.FileName)!;
12    string fileName = Path.GetFileName(dialog.FileName);
13}

The main difference is that WPF returns bool? from ShowDialog() instead of DialogResult.

Multiple Selection

If multiple selection is enabled, use FileNames and parse each full path separately:

1using Microsoft.Win32;
2using System.IO;
3
4var dialog = new OpenFileDialog
5{
6    Multiselect = true
7};
8
9if (dialog.ShowDialog() == true)
10{
11    foreach (string file in dialog.FileNames)
12    {
13        string dir = Path.GetDirectoryName(file)!;
14        string name = Path.GetFileName(file);
15        Console.WriteLine($"{dir} -> {name}");
16    }
17}

This is cleaner than trying to infer shared directory state from only the first file unless your UI explicitly guarantees same-folder selection.

SafeFileName Is Helpful but Narrower

Some dialog implementations also expose SafeFileName, which gives only the selected file name without the path. That can be convenient, but Path.GetFileName(dialog.FileName) is usually more explicit and works consistently with the full-path value you already have.

If you need the directory, SafeFileName is not enough anyway.

Common Pitfalls

The biggest mistake is parsing paths with string operations such as Split('\\') or Substring. That approach is fragile and quickly breaks on edge cases such as UNC paths or unexpected separators.

Another common issue is forgetting to check the dialog result before reading FileName. If the user cancels, the path may be empty or meaningless for the current flow.

Developers also sometimes confuse WinForms and WPF dialog APIs. The dialog classes differ, but once you have the selected path, System.IO.Path is still the right tool in both cases.

Finally, if you are saving files rather than opening them, remember that the selected directory may need to be created or validated separately. Path extraction and file-system existence are different concerns.

Summary

• Read the selected full path from OpenFileDialog.FileName.
• Use System.IO.Path methods to extract directory, file name, base name, and extension.
• Avoid manual string parsing for file paths.
• In WPF and WinForms, the dialog types differ but Path usage is the same.
• Check the dialog result before using the returned path.