解决文件路径太长时间异常的最佳方式 [英] Best way to resolve file path too long exception
问题描述
我创建了一个下载SP站点中的所有文档库的应用程序，但有一点它给了我这个错误（我试着看google但是找不到任何东西，现在如果有人知道任何技巧来解决这个问题，请否则感谢您查看）
I created a app that downloads all document libraries in a SP Site , but at one point it giving me this error (I tried looking at google but couldn;t find anything, now if anyone knows any trick to solve this problem please respond otherwise thanks for looking at it)
System.IO.PathTooLongException：指定的路径，文件名或两者都太长。完全限定文件名必须小于260个字符，目录名称必须小于248个字符。
在System.IO.Path.NormalizePathFast（String path，Boolean fullCheck）
在System.IO.Path.GetFullPathInternal（String path）
在System.IO.FileStream.Init（String path ，FileMode模式，FileAccess访问，Int32权限，Boolean useRights，FileShare共享，Int32缓冲区大小，FileOptions选项，SECURITY_ATTRIBUTES secAttrs，String msgPath，Boolean bFromProxy）
在System.IO.FileStream..ctor（String path，FileMode模式，FileAccess访问，FileShare共享，Int32缓冲区大小，FileOptions选项）
在System.IO.File.Create（String path）
System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck) at System.IO.Path.GetFullPathInternal(String path) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.File.Create(String path)
达到字符串的限制，代码如下：
it reaches the limit for string, Code is given below,
#region Downloading Schemes
private void btnDownload_Click(object sender, EventArgs e)
{
TreeNode currentNode = tvWebs.SelectedNode;
SPObjectData objectData = (SPObjectData)currentNode.Tag;
try
{
CreateLoggingFile();
using (SPWeb TopLevelWeb = objectData.Web)
{
if(TopLevelWeb != null)
dwnEachWeb(TopLevelWeb, TopLevelWeb.Title, tbDirectory.Text);
}
}
catch (Exception ex)
{
Trace.WriteLine(string.Format("Exception caught when tried to pass TopLevelWeb:{1}, Title = {2}, object data to (dwnEachWeb_method), Exception: {0}", ex.ToString(), objectData.Web, objectData.Title));
}
finally
{
CloseLoggingFile();
}
}
private void dwnEachWeb(SPWeb TopLevelWeb, string FolderName, string CurrentDirectory)
{
if (TopLevelWeb != null)
{
if (TopLevelWeb.Webs != null)
{
CurrentDirectory = CurrentDirectory + "\\" + TopLevelWeb.Title;
CreateFolder(CurrentDirectory);
foreach (SPWeb ChildWeb in TopLevelWeb.Webs)
{
dwnEachWeb(ChildWeb, ChildWeb.Title, CurrentDirectory);
ChildWeb.Dispose();
}
dwnEachList(TopLevelWeb, CurrentDirectory);
//dwnEachList(TopLevelWeb, FolderName, CurrentDirectory);
}
}
}
private void dwnEachList(SPWeb oWeb, string CurrentDirectory)
{
foreach (SPList oList in oWeb.Lists)
{
if (oList is SPDocumentLibrary && !oList.Hidden)
{
dwnEachFile(oList.RootFolder, CurrentDirectory);
}
}
}
private void dwnEachFile(SPFolder oFolder, string CurrentDirectory)
{
if (oFolder.Files.Count != 0)
{
CurrentDirectory = CurrentDirectory + "\\" + oFolder.Name;
CreateFolder(CurrentDirectory);
foreach (SPFile ofile in oFolder.Files)
{
if (CreateDirectoryStructure(CurrentDirectory, ofile.Url))
{
var filepath = System.IO.Path.Combine(CurrentDirectory, ofile.Url);
byte[] binFile = ofile.OpenBinary();
System.IO.FileStream fstream = System.IO.File.Create(filepath);
fstream.Write(binFile, 0, binFile.Length);
fstream.Close();
}
}
}
}
//creating directory where files will be download
private bool CreateDirectoryStructure(string baseFolder, string filepath)
{
if (!Directory.Exists(baseFolder)) return false;
var paths = filepath.Split('/');
for (var i = 0; i < paths.Length - 1; i++)
{
baseFolder = System.IO.Path.Combine(baseFolder, paths[i]);
Directory.CreateDirectory(baseFolder);
}
return true;
}
//creating folders
private bool CreateFolder(string CurrentDirectory)
{
if (!Directory.Exists(CurrentDirectory))
{
Directory.CreateDirectory(CurrentDirectory);
}
return true;
}
//shorting string
#endregion
推荐答案
由于错误的原因很明显，以下是一些帮助您解决问题的信息：
As the cause of the error is obvious, here's some information that should help you solve the problem:
以下是链接的引用：
最大路径长度限制在Windows API中（除了以下段落中讨论的一些例外），路径的最大长度
为MAX_PATH，定义为260个字符。本地
路径按以下顺序组织：驱动器号，冒号，
反斜杠，以反斜杠分隔的名称组件，以及一个终止的
空字符。例如，驱动器D上的最大路径为D：\some
256个字符的路径字符串< NUL>其中< NUL>代表当前系统代码页的无形
终止空字符。 （
characters<>在这里用于视觉清晰度，不能是
a有效路径字符串的一部分。）
Maximum Path Length Limitation In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string<NUL>" where "<NUL>" represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)
还有一些解决方法（来自评论）：
And a few workarounds (taken from the comments):
有解决各种问题的方法。下面列出的解决方案的基本思想总是相同的：减少路径长度以便具有 path-length + name-length< MAX_PATH 。您可以：
There are ways to solve the various problems. The basic idea of the solutions listed below is always the same: Reduce the path-length in order to have path-length + name-length < MAX_PATH. You may:
- 共享子文件夹
- 使用命令行通过SUBST
- 在VB下使用AddConnection将路径分配给路径
这篇关于解决文件路径太长时间异常的最佳方式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
