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
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?
Mark Ward commented
Here is an example of Microsoft's own having to work around the limitation
"Avoid path too long errors when performing BuildV2 builds in MVC repo
- do not glob to the ends of the earth when looking for `project.json` files"
Johnny Willemsen commented
This is blocking our migration to msbuild, looks custom build steps add several log files which are now put in a directory that is longer then 260 characters forcing us to stay with nmake
Our company won't be renewing our Microsoft licenses. We won't be buying new versions of Visual Studio. We won't be hosting our web applications and web services on Microsoft technologies. We won't be developing in Microsoft Windows.
Get it yet, Microsoft? By being lazy, you are going to push away the customers who pay the big bucks for your software.
Unfortunately, this renders all of your effort invested into NPM integration in Node Tools for Visual Studio unusable, and therefore effectively worthless. Sorry.
This is a big pain **********, sorry! But we are in 2015. And the Explorer of Windows 10 dosen't support this and also Visual Studio 2015 does not support this.
NTFS etc. support lenght approximately 32.000 chars. Why will Micrososft not Work on that feautre? You have more then 100.000 employees and the price for Visual Enterprice is over 5.000 $
Micrososft will close this Issue, due the high investment cost? Not really!
This is not a cosmetic Bug this a major problem, also for the future life of Microsoft.
Please change your mind.
I hit this issue again today. I can't believe Micro$oft isn't fixing it.
Goran Obradovic commented
What is the point of voting for something if votes are not considered when estimating what is really important to your users and what is of most value for your customers? Obviously you have other tools to estimate what is most value for your customers and to me it is not very transparent how you do it.
Steve Sheldon commented
This problem is all throughout Windows, and I do have to agree with other comments here that eventually this is going to lead many companies to migrate off the platform.
I've hit this issue before with Visual Studio and TFS, surprisingly the project that seems to cause the most paint is a Platform & Practices assembly from several years ago which has like 80 characters in it's name.
We deal with a lot of digital content transmitted to us from vendors where filenames are highly descriptive and may be 100+ characters in length. Copying or moving these files around frequently results in hitting this limit. It's not a problem for our vendors as most are on Linux.
You know what's valuable to me? Fixing the broken system.
"This is something that makes you tear your hair out and buy a Mac." <- Exactly!
Basically, Microsoft has been too busy doing great things like:
-Removing Aero Glass (which most of their customers would actually prefer to have), and producing the ugliest popular (as in "forced on a bunch of unsuspecting users") UI to date.
-Making ugly/gaudy icons (and then receiving backlash and producing yet another set of slightly better icons) when the existing icons were perfectly fine/better than what we have now. (Those of you who didn't participate in the Preview missed out on this fiasco!)
-Mass rewriting core UI functions to slow, memory hogging, and inefficient XAML code when the native Win32 versions we had previously were fine. Most of us Insiders preferred the pre-build 9926 Start Menu, before it was converted to XAML.
-Adding spyware to their system (which many of their users don't want).
...to even care about actually important stuff like this, new technology support, better performance and security in their core OS. It's about time Microsoft should try to keep up with their competitors!
In the meantime, everyone running Windows 10, please open the Windows Feedback app, search for "max_path", and vote up the appropriate suggestion(s). It's the best we can do at this point.
Jack Mott commented
This is something that makes you tear your hair out and buy a Mac.
Igor Varfolomeev commented
This limitation is one of the main things, that make me think that it might be easier to migrate to another OS...
This issue MUST be fixed. It's absolutely unacceptable.
For me it's more important that all other things M$ developed since Windows 7 (e.g. more than Windows 8-10, all recent MS Office versions and all recent versions of MSVS all together). So, for me, "Dedicating resources to this work item would come at the expense of many other features and innovation" is not an answer.
Eventhough I appreciate your answer from October 2013, I'd like to give this is issue an up-vote.
Today is July 2015. Please keep communicating with your customers. Thank you.
As much as I understand this is a major architectural change, it is a fundamental issue that we don't expect to encounter on a post-1990's computer. Not allowing file path strings that are allowed by the operating system demonstrates a failure to accomplish the most basic aspect of file IO. The idea that other features would not come out as a consequence is unfortunately necessary. People would rather have something that works reliably than something with tons of broken features. Heaven forbid the new model of toaster lacks a laser light show because they had to go back fix the issue of it not actually making toast.
Bumping this up again , this issue comes up too often in the context of developing in vstudio especially for web/mobile development. Instead of blanket must fix everywhere , please take a single usecase and figure out how to make it work. The customer below working in node is an excellent place to start. I used to PM at msft and am well aware of the top down planning done there, its time to change or lose more developers to the droid / ios world.