Fix 260 character file name length limitation
The 260 character limit on file paths really gets in the way of having a deeply-nested project hierarchy. It's only there as backwards compatibility with the old school APIs, and has no place in any sort of modern development environment.
We should be able to work with file paths of whatever size we want.
Hello everyone and thank you for the feedback and for voting on this issue. We understand that this can be a frustrating issue, however, fixing it requires a large and complicated architectural change across different products and features including Visual Studio, TFS, MSBuild and the .NET Framework. Dedicating resources to this work item would come at the expense of many other features and innovation. Additionally, if we removed this limitation from our first party tools it will still likely exist elsewhere in Visual Studio’s ecosystem of extensions and tools. For these reasons, we are declining this suggestion and returning return everyone’s votes so they can be applied to other items. In the interest of delivering the most value to our customers we sometimes have to make very difficult cuts, and this is one of them.
Visual Studio – Project and Build Team
Was this seriously declined? We already shortened the paths however we could, but our build is still failing. EPIC FAIL.
Any update on this issue?? Two years later...
I miss you Linux!!!
Shockingly stupid... Why did I get away from developing in Linux environments?
This is a massive problem for organizing and backing up information. Descriptive file names and logical folder structures have to go out the window for the sake of accommodating this. How are businesses supposed to cope with this?
Yet another reason why people are moving away from Microsoft products. Just because it's hard, that's no reason to ignore such a fundamental problem.
Markus Hopfenspirger commented
Now it is definitely time to reopen this issue!!!!
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!!!
Mark Ward commented
There are more comments than characters allowed in a file name path.
seeing the following in TFS online
Invalid path for filesystem 'C:/agent <path>
: The data area passed to a system call is too small.
Any fix around this
Jijie Chen commented
We really really want to work with file paths of whatever size we want. Many thanks to great Microsoft!
Josh Williams commented
...... 260'th comment ...... the irony .... the agony .....
This problem makes the npm tooling in VS 2015 pretty much useless.
Please, please, please remove this ridiculous restriction.
Geez... What year is this already? Feels like 1990s and tearing my hairs out even after windows 10
I think this limit is a usefull feature.
Try using Long Path Tool program. This is very useful.
I am using a software called Long Path Tool and it is working like charm, i have no problems in copying or extracting anything anywhere.
Bryan Rayner commented
Two days lost because I effectively can't use npm in a .Net MVC project. Microsoft has been getting so much better - Typescript is amazing. Why can't this be improved?