.NET从SQL Server读取长文件名Excel后无法打开问题求助

Hey there, let's break down why your exported Excel file won't open even after adjusting your SQL Server fields. Here are the most likely culprits and fixes to try:

1. Check the full path length (not just the filename) #

Windows has a traditional path length limit of 260 characters (including the entire directory path + filename). Even though your 103-character filename works when you manually create it in a short path, your Debug folder's path might already be long enough that adding the 103-character filename pushes the total over 260.

For example:

• If your Debug path is C:\Users\YourName\Documents\Visual Studio 2022\Projects\ExcelImporter\ExcelImporter\bin\Debug\net7.0 (let's say that's ~120 characters), adding a 103-character filename gives you a total of ~223, which is under 260—but if you have extra suffixes/prefixes in your save logic (like Export_FileName.xlsx), that could tip it over.

Fix:

• Calculate the full path length when saving the file. You can print it in your code with Path.GetFullPath(savePath) to check.
• Try saving the file directly to a root directory like C:\ temporarily. If it opens fine, you know the issue is the long combined path.

2. Look for hidden or invalid characters in the stored filename #

Sometimes user-uploaded filenames contain invisible control characters (like line breaks, non-breaking spaces, or special Unicode characters) that aren't obvious. Even if the filename length shows as 103, these characters can cause Excel to misinterpret the filename as longer or invalid.

Fix:

• In your database, run SELECT LEN(AttachmentName), ASCII(SUBSTRING(AttachmentName, N, 1)) FROM YourTable (replace N with each position from 1 to 103) to check for odd characters.
• Clean the filename in your .NET code before saving it. For example, strip out non-printable characters with a regex:

using System.Text.RegularExpressions;

// Clean invalid characters from the filename
var sanitizedFileName = Regex.Replace(originalFileName, @"[^\w\.\- ]", "_");
// Also trim any leading/trailing whitespace
sanitizedFileName = sanitizedFileName.Trim();

3. Ensure your .NET app supports long paths #

Newer .NET versions allow long paths, but you need to explicitly enable it. If your app isn't configured to handle paths over 260 characters, it might be saving the file in a way that causes Excel to throw errors.

Fix:

• For .NET Framework: Add this to your app.config:

<runtime>
  <AppContextSwitchOverrides value="Switch.System.IO.UseLegacyPathHandling=false;Switch.System.IO.BlockLongPaths=false" />
</runtime>

• For .NET Core/.NET 5+: Add this to your project file (*.csproj):

<PropertyGroup>
  <EnableWindowsLongPaths>true</EnableWindowsLongPaths>
</PropertyGroup>

4. Verify your save logic isn't modifying the filename #

Double-check if your code is adding extra text to the filename when saving (like a timestamp, export prefix, or duplicate extension). For example, if your code does something like $"Export_{AttachmentName}{AttachmentExtension}", you might be accidentally doubling up the extension (e.g., file.xlsx.xlsx) or adding unnecessary length.

Fix:

• Debug your save logic and print the final filename before writing the file to disk. Make sure it exactly matches the valid filename you tested manually.

Give these steps a try—chances are one of them will resolve the issue!

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