Fix 260 character file name length limitation
We’re actively looking into addressing this issue in .NET Core and .NET Framework. You can find a design the design proposal we shared publicly here:
Immo Landwerth, Program Manager .NET
gamick lisafisher commented
Long Path tool can be used to handle this solution.
If I could, I'd add 9999999 votes to this. This is an epic failure, I cannot sum it up in any other way. If this persists with Windows in the future, we will consider dropping it. Products get more and more complex and you cannot justify not fixing it in any way.
Mark Aurit commented
This is so sad. Please fix it.
Immo Landwerth [MSFT] commented
> You're addressing the issue at the .NET level? That's the wrong layer, and won't help any of the native code out there. At best it's a token effort.
No worries. We're working with the Windows team to see what could be done there, too.
The big driver for this was Node, or more specifically npm, which put dependencies of each package into a subdirectory, and ended up creating hugely nested folder structures that were untenable under Windows. But strangely enough, node has recently mitigated this problem with the release of Node 5.0.0, which also includes npm 3.0. The latest version of npm 3.0 no longer nests paths, so the long pathname issue in Windows becomes moot. In fact, one reason npm 3.0 reordered the paths was specifically to mitigate the long pathname problem in Windows.
So I guess the pressure to address the problem immediately is lessened. Kudos on addressing it though - long pathnames should not be insurmountable within Windows.
You're addressing the issue at the .NET level? That's the wrong layer, and won't help any of the native code out there. At best it's a token effort.
Fix it! This comes off as a fundamental OS issue! What else can Microsoft do right, if they can't get the file system right?
Turning off your developer community is a major step towards your demise.
Markus Hopfenspirger commented
Need to be fixed in Windows 10 Explorer or Windows 10 in general too... See Windows User Voice (also over 3400 votes) https://windows.uservoice.com/forums/265757-windows-feature-suggestions/suggestions/6573539-remove-the-long-standing-max-path-limitation
- Visual Studio produces very long file paths e.g. when using Service References witch lead to problems using TFS Builds
- Many Open Source Projects are not limited to MAX_PATH
- Many cloud storage systems are not limited to MAX_PATH
- Customers using document management Systems complain more and more about not being able to sync with Windows
- Zip or other Archive Files are not limited to MAX_PATH and can not be Opened wir Windows Explorer and can not be unpacked on Windows
I see, that removing the Limit is not an easy task, but it has to be done in the near future!!!
And you want me to buy a surface book. :)
Hey news flash, the problem with the surface book isn't the hardware. It's windows. Because of stupid **** like this.
... written on my Macbook Pro
No worries, I'll just convince my employer to get off Windows Server 2012 and onto linux. Your right Microsoft, this isn't important.
Josh Williams commented
*Releases badass support for Node in VS*
*Cant create / run Node projects in VS due to insane pathing in node_modules*
Roberto Paterlini commented
Can't do a branch in TFS because 'Add service reference ...' on a xamlx service create a file 173 char long !!!
Warning 'Long Path Tool' will NOT work in Visual Studio with long paths e.g. Node development work etc.
To use "package" with long paths you'll either have to develop on Linux or a Mac.
I'm a front end developer using Angular, React and Node. Long pathed packages such as Mocha and other goodies will not work on Windows.
If you want a good IDE for Linux or Mac try using WebStorm instead
Definitely need a fix for this issue cause i can't use sqlite3 node.js module and then remote debug my project on raspberry pi (WinIOT)
Duy Trung Trần commented
I cannot install mongo-db modules in node.js project due to this issue. Please fix it
Maxime Briziarelli commented
Now that Node Tools for Visual Studio are out, MS MUST fix this problem.
You should check out 'Long Path Tool' it will help you fix the issues.
.NET Core is adding support
I'm now forced to run some NodeJS projects inside a Docker VM on windows because of this ridiculous file limit.
LS Dev commented
MIcrosoft, has this issue been addressed/fixed in Windows 10???
Or are we going to be stuck with this 260-character for the next decade as well? Surely there was something to be learned from the infamous assumption that "we'll never need more than 640K RAM".
Yes 3 votes for this issue too. 2600+ votes must be pretty high up on the tree. Disappointing to see the slow adoption for fundamental issues such as path length, 64-bit tooling, running dot net processes as 64-bit (we had to fight tooth and nail to stop the default being x86 which is pretty incredible), 64-bit EnC. Those things are really foundation blocks for the dev platform but Microsoft tends to toss them straight into the "too hard basket".