I suggest you ...

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.

3,002 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Steve LeighSteve Leigh shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Visual Studio UV Site AdminAdminVisual Studio UV Site Admin (Admin, Microsoft) responded  · 

    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.

    Thank you,

    Will Buik,
    Visual Studio – Project and Build Team


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      • Anonymous commented  ·   ·  Flag as inappropriate

        @Will Buik - This is a ridiculous answer to a problem that everyone using Windows in a professional way comes across. I am astonished that you feel this problem is not important enough to fix.

        This is 2014 and problems like this should simply not exist in a modern operating system. It reminds me of the problem with VARCHAR in SQL server - the limit of 8000 characters was a pain and using TEXT columns was not an acceptable answer. Now we have VARCHAR(MAX) and (almost) everyone is happy. You have to stop carrying the technical debt into new versions and draw a new base line at some point. That point is now.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Absolute crock of cr*p, this is typical - oh it's too hard, and we're adding stuff nobody asked for or really needs rather than fixing critical stuff in the background... *sigh*

      • William BosackerWilliam Bosacker commented  ·   ·  Flag as inappropriate

        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!


      • Arjen van PuttenArjen van Putten commented  ·   ·  Flag as inappropriate

        Is there anyone with a workaround for this issue? I changed my IntermediateOutputPath already to almost root..

      • MichaelMichael commented  ·   ·  Flag as inappropriate

        This limitation is such a pita to work around. Pretty much adding 1 or 2 folders to your VS project and you risk hitting this in TFS.

        So because it is a lot of work the feedback is declined? That is pretty poor customer service. Delivering the most value to your customer would be delivering that which is being asked for by your customer.

      • Colin BowernColin Bowern commented  ·   ·  Flag as inappropriate

        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:


      • Matthias GoetzkeMatthias Goetzke commented  ·   ·  Flag as inappropriate

        So the reasoning is to not fix it ever because it a lot of work. They could have said we t take out the limitation step by step .. And realistically they should have started doing that years ago. Thru would have finished by now and the few extensions not following this would have been shunned.. But Ms doesn't really have pride in what they deliver. It's a little like s showing the finger to the people that removed this limit from the fs.

      • William BosackerWilliam Bosacker commented  ·   ·  Flag as inappropriate

        @anthonyk: As I told you in the other thread, LPT does nothing for VS or TFS. The limitation is hardcoded into the applications themselves, along with the hard coded limitation of the .NET Framework, and LPT does absolutely nothing to change that.

      • anthonykanthonyk commented  ·   ·  Flag as inappropriate


        Simply download new Long Path Tool software that simply allows you to work easily on Long Path files.

        Thank you.

      • Adam VelebilAdam Velebil commented  ·   ·  Flag as inappropriate

        I can't decide what is more ridiculous - the limitation itself or the fact that the suggestion to fix it was declined.

      • William BosackerWilliam Bosacker commented  ·   ·  Flag as inappropriate

        @James Neave: The majority of us don't map TFS to a folder under "My Documents", we're already using a short path like C:\Work or C:\TFS, and we're still running into the 260 character barrier. Try working on a large web application, or creating multiple libraries, and you'll run into the same problem.

      • James NeaveJames Neave commented  ·   ·  Flag as inappropriate


        One workaround we use is thus:

        We have our Projects folder in My Documents, under that lots of long, descriptive branch names and random failures due to path length.

        But we get around it by mapping the Z: drive to that Projects folder.
        It does cause issues where that drive isn't mapped under all the user accounts you need but I'm sure that could be solved as well.

        We also use it in build scripts for various things, there we use the subst command to point a driver letter at a folder on a local disk.

      • Mark BentleyMark Bentley commented  ·   ·  Flag as inappropriate

        Wow, and 256K is good enough for anyone (Bill Gates). This is a really dumb and out of date limitation. Now I have to impose a poor design on my project tree structure to work around your 1980s path limitations.

      • AnonymousAnonymous commented  ·   ·  Flag as inappropriate

        Large architectural change?!?!
        In any databases instead of *CHARTYPE*(260) use *CHARTYPE*(*REALISTIC-NUMBER*) ..... And in code, instead of fixed length character arrays, malloc some heap space and use char pointers and nul terminated strings. And fix it incrementally in each product as the problem is encountered. How has this bug not slowly gone away over ~15 years of code refactoring/updating/replacement. Are all your file & directory names only 8 characters + 3 character extension, all uppercase... or has that limitation been phased out yet?

      • Anonymous commented  ·   ·  Flag as inappropriate

        All the innovation if we're still haunted by such extreme legacy? Really?

        Many applications could break, but they would still work as long as the paths are within 260 characters.

        What's the drawback? I don't see it.

      • Eric BrownEric Brown commented  ·   ·  Flag as inappropriate

        Given this one was "DECLINED" by Will Buik, the community has responded with: Your reason is not good enough and we STILL want this fixed. Another entry for this item was made here: https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4954037-fix-260-character-file-name-length-limitation#comments Please vote on it so we can hopefully get Will's lame response reversed and have Microsoft address this issue once and for all. Thanks!

      • Anonymous commented  ·   ·  Flag as inappropriate

        Absolutely insane that in this day an age, a 260 char file path limit would be imposed for absolutely no reason whatsoever. We don't NEED "other features and innovation". We need basic functionality to work when expected.

      • Rob ScottRob Scott commented  ·   ·  Flag as inappropriate

        I have to conclude that you have a very poor tightly-coupled architecture. This is pretty surprising given that loose-coupling is Computer Science 101. I will be dropping TFS for version control. Perhaps when you lose enough customers the issue will be "frustrating" enough for you to reconsider.

      ← Previous 1 3 4 5 8 9

      Feedback and Knowledge Base