I suggest you ...

4,542 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    ScottLanghamScottLangham shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    120 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Rivera CookRivera Cook commented  ·   ·  Flag as inappropriate

        Sometimes we get an error when we try to delete a File or a folder for no reason , but of course there is a reason.We have many damage file or blocked files.Do not worry if we want to remove the error files or too long path files from our system,here I suggest a smooth way.So use “Long path tool” software and keep yourself.

      • howard brookshoward brooks commented  ·   ·  Flag as inappropriate

        The Long path tool is the very best program for error, unlock solution.
        Try it and solved your problem.
        I used the long path tool and I solved my error, unlocks problem solution.

      • prpr commented  ·   ·  Flag as inappropriate

        Can you confirm, that on Windows 2012r2 System.IO.Directory still has Problems with long paths even if a c# Applciation is build with/to .Net 4.6.2 ?
        I have in Windows10 the Registry/Policy switch "Enable Win32 long path" which is missing in Server 2012r2.
        Greetings and Thanks for any Help
        Philipp

      • aiden carteraiden carter commented  ·   ·  Flag as inappropriate

        The Long path tool is the very best program for error, unlock solution.
        Try it and solved your problem.
        I used the long path tool and I solved my error, unlocks problem solution.

      • Anonymous commented  ·   ·  Flag as inappropriate

        “Long Path Tool” is very helpful for this error !
        best solution for your problem.

      • johnrafjohnraf commented  ·   ·  Flag as inappropriate

        “Long Path Tool” is very helpful for this error !
        You can use to solve this problem.

      • Griffin001Griffin001 commented  ·   ·  Flag as inappropriate

        you can try Long Path Tool to solve your problem. it can shorten your file path name and find the root source. The fun part is its easy to use and its totally free.

      • Eric BrownEric Brown commented  ·   ·  Flag as inappropriate

        AWESOME news! Thank you for fixing this rather than just closing it and ignoring the outcry. It took the community quite a bit of effort to get to this point, but, I'm glad to see the effort has paid off! :)

        Thank you to everyone who has persisted in clamoring for getting this corrected and more importantly, thank you to the team that eventually fixed this! It's MUCH appreciated!

      • FredFred commented  ·   ·  Flag as inappropriate

        16 years for this bug since XP was released and not fixed?

        My guess is it is a rewrite of a good part of the NT based operating system and higher in the risk category.

        Deprecate the limited win32 calls, replace them with longer path ones, rewrite the .NET parts, move MS products using the deprecated win32 calls to the longer path ones, ...
        remove the deprecated ones in a future Windows version.

      • William BosackerWilliam Bosacker commented  ·   ·  Flag as inappropriate

        On the .NET VLOG for Thursday, June 23, 2016, it was announced that .NET Framework 4.6.2 has the ability to use long path names and the extended syntax. .NET Core has had this functionality since last fall (2015). They also go on to say that the Windows Team is working on the issue for Windows itself.

        What does this mean? NTFS has supported long path names (up to ~32768 characters) since XP was first released, but only via the Win32API and by using extended path names. .NET was never given access to this, until now. Windows has always had access to this since XP, but never used it. I would guess that Windows will have full access to long paths before the end of 2016. Once you have .NET Framework 4.6.2 installed on a machine, PowerShell will immediately have access to long path names as well.

        ENJOY!

      • Jahanzeb SayalJahanzeb Sayal commented  ·   ·  Flag as inappropriate

        Microsoft!!! Please eat this FROG now ... you have to eat it at some time in future ... better NOW than later .... in my opinion...
        Thanks for reading.

      • EricTNEricTN commented  ·   ·  Flag as inappropriate

        I'm probably a bit confused here, and/or I'm stating something that's been stated repeatedly already in several of the 100 comments that have already been made, but: isn't this a Windows problem, not a .NET problem? When npm has its way with my workstation, inevitably it throws a couple 100 files in a DEEPLY-nested spider-web of folders inside folders inside folders inside folders inside.... ok.. you get the idea, and you already know that. I can't get **WINDOWS** to deal with that, let alone .NET. Maybe I'm missing something. I try to move this vast impenetrable web of folders from one spot to another on my hard drive, and it would appear that WINDOWS refuses to do it. So.... sorry if I'm not even talking about something relevant here.

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base