Fix 260 character file name length limitation
Long Path Tool is the most appropriate program to sort out such issues..............
FYI, every single one of these references to "Long Path Tool" are from the same person, the author. Whenever you see a post like those, please click the "FLAG AS INAPPROPRIATE" link, as he is trying to sell his tool through this and other sites.
Martin Müller commented
Everybody please stop mentioning “Long Path Tool” as it absolutely has nothing to do with this suggestion. (Excercise: Why?)
Wahid Haq commented
I suggest everyone to try "Long Path Tool" program. It’s really work for me.
u can try using long path tool. i think its good solution for ur problem :)
260 characters - that is like 640k of memory. This restriction was ridiculous even when while it was introduced! This is plain bug and costs more time and money than all the productivity Windows possibly provides.
shouldn't even have to ask for this...this isn't even a feature request ....
this is a ignored bug a relic from the Ancient times of windows
someone should be assigned to.
1) force the error track it down , i.e. find the line
were the path file length limit = 260
2) then set it to like 2,600 or something
so we never have to worry about it again in our lifetimes
3) stick the fix in the next windows update
I have just tested Windows Server 10 technical preview build 9481 (which is Windows version 6.4) and I am astonished and disappointed to say this limitation still exists in the operating system so there is no chance of it being fixed in Visual Studio or TFS.
Here is hoping this is going to be resolved before the final release however this is such a low level thing you would think it would be in the preview.
ridiculous is straight to the point.
Guys come on, in the year 2014 we are talking about 260 character limits... this is ridiculous.
Jim Palavros commented
Can anyone confirm that the "Long Path Tool" Software really works? If so, can I get a link. I don't want to play around with any downloads that may have different intentions.
Hey All, this "Long Path Tool" does absolutely nothing for us, and the author of the tool spams it all over the place, like the message below. This issue has been around for over 12 years, so I have created an issue on Microsoft Connect to fix this BUG! If everyone would go to the URL below, login, and Click the up arrow to vote for this, Microsoft will be forced to respond. While these uservoice forums are helpful, they aren't actually tracked in Microsoft's issue system. Microsoft Connect is the public portal to their issue system. PLEASE VOTE!
you are welcome
Long Path Tool is the most appropriate program to sort out such issues
I have added 3 votes to this. The original decline is not acceptable.
Colin Bowern commented
I think you need to start chipping away at this problem. Node.js re-introduces this as well:
I had to write a TFS build activity that could handle cleaning up node modules:
Omar Rashwan commented
It's absolutely ridiculous that I can't create a directory without running into a character limit. All other operating systems don't have this archaic restriction, especially not in this millennium. I would gladly sacrifice any features we miss out on in the time it takes to fix this bug.
@anthonyk: LPT does nothing to extend TFS or VS. LPT is a stand alone application for managing your file system. It does nothing to allow TFS or VS to access long filepaths, which is the purpose of this idea.
Simply download new Long Path Tool software that simply allows you to work easily on Long Path files.
With the release of Windows XP over ten years ago, Windows has supported a file path length of 32,768 characters where each individual folder/file segment name is limited to 256 characters, and the Windows API has supported this from day 1. There is absolutely no valid reason, or excuse, that for over 10 years the .NET Framework still does not support this. The same goes for TFS, which should have supported this on it initial release.
It would be AWESOME if you at Microsoft would pull your heads out of your ***** and fix this. Steve Ballmer is out! Who is the next person that needs to be removed to get this accomplished? Business as usual just won't cut it any longer.
Eric Brown commented
The vote count continues to climb on this suggestion. It is my hope that Microsoft will decide that simply declining this suggestion is only going to result in yet another suggestion of the same type to be created. This cycle will likely repeat itself until Microsoft decides enough is enough and dedicate development resources to correcting this ridiculous issue. Thanks!