blocks|key|221704|text|这是Windows+win32+api中的一个众所周知的限制。存储项目的目录嵌套太深。文件的完整路径名不能超过259个字符。除此之外，由于缓冲区溢出，许多使用MAX_PATH的C代码开始失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|221705|将您的解决方案移动到另一个更接近根目录的目录。|221706|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This is a well-known restriction in the Windows win32 api. The directory in which you stored your project is nested too deep. The full path name of a file cannot contain more than 259 characters. Beyond this, lots of C code that uses MAX_PATH starts failing due to buffer overflows.

Move your solution to another directory, one that's closer to the root.

blocks|key|2871664|text|我遇到过类似的问题，编译器报告ASPNETCOMPILER文件有问题。实际的问题是，解决方案包含一个node_modules文件夹，而该文件夹可能包含非常长的路径，而且看起来编译器无法处理此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2871665|Windows+8.1和Windows+10提供了增加Win32路径限制的选项：|2871666|2871667|打开组策略编辑器(按Windows%2BR键，键入gpedit.msc并按Enter键)|unordered-list-item|2871668|从组策略编辑器窗口中，导航到以下节点:本地计算机策略\计算机配置\管理Templates\System\Filesystem|2871669|Doubleclick上的启用Win32长路径选项并将其启用。|2871670|2871671|这可能允许您临时将问题文件夹移出生成，这可能允许您成功生成，然后您可能能够将该文件夹添加回解决方案中，而不会影响任何内容。|2871672|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|V|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

I had a similar issue where the compiler reported that there was a problem with the file ASPNETCOMPILER. The actual issue was that the solution contained a node_modules folder, and this folder can contain very lengthy paths, and it looks like the compiler can't handle this.

Windows 8.1 and 10 have an option to increase the Win32 path limit:

<ul>
<li>Open Group Policy Editor (Press Windows+R and type gpedit.msc and hit Enter)</li>
<li>From the Group Policy Editor window, navigate to the following node: Local Computer Policy\Computer Configuration\Administrative Templates\System\Filesystem</li>
<li>Doubleclick on Enable Win32 long paths option and enable it.</li>
</ul>

This may allow you to temporarily move the problem folder out of the build, which may allow you to successfully build, then you may be able to add the folder back into the solution without affecting anything.

blocks|key|218644|text|至少可以在Windows+10上使用注册表方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|218645|参数HKLM\SYSTEM\CurrentControlSet\Control\FileSystem+LongPathsEnabled+(Type:+REG_DWORD)的值应设置为1。|offset|length|style|CODE|218646|📷|atomic|218647|你甚至不需要重启任何东西(IDE或PC)。|218648|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/db00dd35c6c3d30f5c7d63d735e99f98.png|imageAlt^0|0|2|2B|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]]]

There is registry approach which can be used at least for Windows 10: 
Value of the parameter <code>HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled (Type: REG_DWORD)</code> should be set to 1.
<a href="https://i.stack.imgur.com/MwEfU.png" rel="noreferrer"><img src="https://i.stack.imgur.com/MwEfU.png" alt="enter image description here" /></a>
You don't even need top restart anything (IDE or PC).

blocks|key|2871835|text|此问题是由于Windows操作系统对处理长度大于260的长路径的限制造成的。对于VS2019来说，这个问题的解决方案非常简单。但是，对于VS2017用户，我们可以使用一个变通方法来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2871836|VS+2019|offset|length|style|BOLD|2871837|2871838|打开run窗口(-|unordered-list-item|CODE|2871839|%2B+r)，然后键入regedit并按enter。|2871840|在注册表编辑器的地址栏上，输入以下内容:清除右侧，找到注册表项LongPathsEnabled，双击它，然后将值从0更改为windows+VS2019，清除(如果需要)并重新构建项目。应修复此错误。|2871841|2871842|2871843|常规解决方法(VS2017/VS2019)|2871844|我们可以创建从原来的较长路径到较短路径的链接。然后，VS会将较短的路径作为项目根，问题就会得到解决。|2871845|打开项目创建一个较短的根路径，例如，我们已经创建了directory|2871846|Now+|2871847|(命令提示符)，并使用以下命令创建了一个符号链接："D:\project"您可能需要以管理员身份打开cmd如果上述命令现在无法执行|2871848|，请从"D:\project\myProject"目录打开VS项目，它应该可以工作。|2871849|2871850|2871851|entityMap^0|0|0|7|0|0|2|3|1|9|7|1|V|G|1L|1|1|0|0|0|L|0|0|0|0|P|C|0|3|M|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1D|8|@$D|1E|E|1F|F|L]]|9|@]|A|$]]|$1|M|3|N|5|K|7|1G|8|@$D|1H|E|1I|F|L]]|9|@]|A|$]]|$1|O|3|P|5|K|7|1J|8|@$D|1K|E|1L|F|L]|$D|1M|E|1N|F|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Q|8|@$D|1R|E|1S|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1T|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|K|7|1V|8|@]|9|@]|A|$]]|$1|10|3|11|5|K|7|1W|8|@$D|1X|E|1Y|F|L]]|9|@]|A|$]]|$1|12|3|13|5|K|7|1Z|8|@$D|20|E|21|F|L]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|17|$]]

This problem is caused by the restriction of Windows OS about handling long path greater than length 260. The solution of this problem for VS2019 is pretty straight-forward. But, for VS2017 users, we can use a workaround to solve the problem.
VS 2019
<ul>
<li>Open <code>run</code> window (windows-key + r), then type <code>regedit</code> and hit enter.</li>
<li>On the address bar of Registry Editor, enter this: <code>HKLM\SYSTEM\CurrentControlSet\Control\FileSystem</code></li>
<li>On the right side, find the key <code>LongPathsEnabled</code>, double click on it, and change the value from <code>0</code> to <code>1</code></li>
<li>Restart VS2019, clean (if needed) and build your project again. The error should be fixed.</li>
</ul>
General workaround (VS2017/VS2019)
We can create a link of the original longer path to a shorter one. Then, VS will treat the shorter path as project root and the issue will be solved.
<ul>
<li>Create a shorter root path for project, e.g. we have created <code>&quot;D:\project&quot;</code> directory</li>
<li>Now open cmd (Command Prompt) and Create a symbolic link using this command: <code>mklink /D &quot;D:\project\myProject&quot; &quot;YOUR_ACTUAL_LONG_PATH_PROJECT_ROOT_DIRECTORY&quot;</code> [You may need to open cmd as administrator if above command fails to execute]</li>
<li>Now, open VS project from the <code>&quot;D:\project\myProject&quot;</code> directory and it should work.</li>
</ul>

blocks|key|223528|text|不会因为路径名太长而出现worry....This错误，假设您的项目文件夹名为"myproject“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|223529|您只需将您的项目"myproject“更改为D:\myproject或F:\myproject+drive.Then即可发布again..Its+work...|223530|快乐的编码...|223531|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

No worry....This error comes because of long path name,Suppose your project folder name is "myproject".

You Just Change location of project folder...Put your Project "myproject" to D:\myproject or or F:\myproject drive.Then You Publish again..Its work...

Happy Coding...

blocks|key|2871556|text|生成定义工作区“生成代理文件夹位置”VS添加路径存在问题示例：$(SourceDir)+E：\Somedirectory\项目名称\只需将$(SourceDir)保存在文件中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2871557|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It is issue with build defination workspace "Build Agent Folder location"
VS adds paths example:
$(SourceDir)E:\Somedirectory\ProjectName\
Just keep $(SourceDir) in filed

blocks|key|2871617|text|我也有同样的问题。我的结帐路径比CI服务器上使用的路径短。它在CI服务器和我所有同事的机器上构建正常。我们的路径长度相同，因为我们公司有固定长度的用户名。我是唯一一台由于路径太长而无法构建解决方案的机器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2871618|如果您转到以下文件夹：|2871619|C:\Windows\Microsoft.NET\Framework|offset|length|style|BOLD|2871620|C:\Windows\Microsoft.NET\Framework64|2871621|C:\Users[UserName]\AppData\Local\Temp|2871622|找到与您的解决方案一起使用的.NET版本，然后删除"Temporary+ASP.NET+Files“文件夹，您认为这些文件夹中的任何版本都会影响您的构建。|2871623|你可以将它们全部删除，下一次构建web项目可能需要更长一点的时间，因为没有预编译的程序集……|2871624|这个解决方案适用于我的一个包含ASP.NET项目的解决方案--它不适用于其他人在回答中提到的ASP.NET项目，除非他们的解决方案也包含WPF项目。|2871625|搜索错误字符串VS会将我带到这里，所以我认为它可能对其他人有帮助，如果不是Op处理WPF构建问题的话。|2871626|如果这些操作失败-您可以尝试递归地搜索解决方案根目录，以查找路径大于260的文件/文件夹，方法是执行以下操作：|2871627|2871628|Open+Powershell|unordered-list-item|2871629|cd+<path+to+solution+root>|CODE|2871630|cmd+/c+dir+/s+/b+%7C?+{$_.length+-gt+260}+>+output.txt|2871631|2871632|这将通过管道将路径>+260的文件列表传送到将在解决方案的根目录中新创建的output.txt文件。|2871633|这将帮助您查找解决方案中过长的文件。|2871634|entityMap^0|0|0|0|Y|0|0|10|0|0|11|0|0|0|0|0|0|0|0|3|N|0|0|1G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1E|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1F|8|@$F|1G|G|1H|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1I|8|@$F|1J|G|1K|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1L|8|@$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1O|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1P|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1R|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1S|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|1U|8|@]|9|@]|A|$]]|$1|11|3|12|5|10|7|1V|8|@$F|1W|G|1X|H|13]]|9|@]|A|$]]|$1|14|3|15|5|10|7|1Y|8|@$F|1Z|G|20|H|13]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|22|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|23|8|@]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|24|8|@]|9|@]|A|$]]]|1C|$]]

I had the same problem. My checkout path was shorter than the path used on my CI server. It built OK on the CI server, and all my colleagues machines. Our paths are the same length because our company has fixed length user names. I was the only machine that could not build the solution due to long paths.

If you go to these folders:

C:\Windows\Microsoft.NET\Framework

C:\Windows\Microsoft.NET\Framework64

C:\Users\[UserName]\AppData\Local\Temp

Find the version of .NET you are using with your solution, then delete the "Temporary ASP.NET Files" folders from which ever versions you think are effecting your build.

You can delete them all, your next build of a web project might take a little bit longer as there will be no pre-compiled assemblies...

This solution worked for me on a solution containing ASP.NET projects - it wont work on WPF projects that others have mentioned in their answers, unless their solution also contains ASP.NET projects.

Searching for the error string VS gives you brought me here, so I figured it might help someone else, if not the Op with a WPF build issue.

If these fail - you can try searching your solution root recursively for files/folders with paths that are greater the 260, by performing the following:

<ul>
<li>Open Powershell</li>
<li>cd <code>&lt;path to solution root&gt;</code></li>
<li><code>cmd /c dir /s /b |? {$_.length -gt 260} &gt; output.txt</code></li>
</ul>

This will pipe a list of files with paths > 260 to the output.txt file which will be newly created in the root of your solution.

This will help you find files within your solution that are too long.

I'm having trouble while building my WPF solution. Everytime I try to build it, I get this error message: 

<blockquote>
 Unknown build error, '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.'
</blockquote>

Someone can help me? I've already verified all the fields and their extension paths are ok. Can this be a problem with the TortoiseSVN or something like this? I recently added a folder to my solution, can be something with this?

Visual Studio unknown build error. The fully qualified name must be less than 260 characters

我在构建WPF解决方案时遇到了问题。每次我尝试构建它时，都会收到这样的错误消息：未知生成错误，“指定的路径和/或文件名太长。完全限定的文件名必须少于260个字符，目录名必须少于248个字符。”有人能帮我吗？我已经验证了所有的字段和它们的扩展路径都是正确的。这会是TortoiseSVN或类似的问题吗？我最近在我的解决方案中添加了一个文件夹，可以用它来做点什么吗？

问Visual Studio未知生成错误。完全限定名称必须少于260个字符
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio未知生成错误。完全限定名称必须少于260个字符EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio未知生成错误。完全限定名称必须少于260个字符
EN