Fix 260 character file name length limitation
Will Buik already declined it
please solve this problem :(
I am too running into this problem. Very annoying!
@Stelvio How to you tell TFS to use your link instead of the full path?
Well, I found a workaround that ALLOW work with path with more than 260 chars.
Disclaimer: I've tried this trick only on Windows 8 x64 and Visual Studio 2013
So, to make it work I've just create a junction to the folder with the mklink command:
Assume this is the original path: d:\very\very\long\path\to\solution\folder, you can obtain a short link as d:\short_path_to_solution_folder just jaunching this command from a dos shell as administrator:
mklink /J d:\short_path_to_solution_folder d:\very\very\long\path\to\solution\folder
change source and destination path to you needs
This is a ridiculous issue that pops up at the most annoying times and is hard to work around. You and your team come up with a great project structure. You go Publish BOOM "path error" because WCF creates ridiculously long paths in the proxy files and although Visual Studio was able to create them (and use them!) you can't copy them?!?! Fine. You move your project to the root (lots of issues around that, but I digress).... a few months down the rood BOOM "path error", this time because App_Themes creates a fairly deep tree structure. I hear Node.js is unusable because of this too.
I can't push a git commit because of this f***ing bug. ANNOYING THAT I HAVE TO MOVE MY PROJECT TO ROOT C:\ IN 2015.
Its a joke that this still exists :/
Opensource all your ****** products, and let the community help you MS.
Reinhard Kuhn commented
Lets face it: this "uservoice" site has become a dead end ... no one is listening on the other side.
Long Path Tool is the most appropriate program to sort out such issues
Eric Brown commented
Let's get this fixed Microsoft, it's getting to the point where rather than face the wrath of the community and declining it, you're choosing to ignore it. Can we please get this fixed? I'd rather us Linux which doesn't have this problem than to continue to fight with this issue over and over.
Here from the previous issue. This would be a great step forward for the platform along with 64-bit tooling. E.g. the Visual Studio IDE incredibly is still a 32-bit process.
Long Path Tool is the most appropriate program to sort out such issues..............
William Bosacker commented
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