4 ms·

It was fixed in .net 4.6.2 [0] [0] https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcing-net-framework-4-6-2/ https://blogs.msdn.microsoft.com/dotnet/2

• Arnavion 10y ago
  It was fixed in Windows :) Any application can add a manifest entry to enable long paths. The .Net change is because .Net needed to expose / add support for it in addition to the base OS supporting it.
• ploxiln 10y ago
  Wow, fixed in 2016. As I recall, this was marked "wontfix" in 2013: https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/2156195-fix-260-character-file-name-length-limitation https://visualstudio.uservoice.com/forums/121579-visual-stud... It's been _possible_ using the NT Unicode APIs since Windows 2000: https://msdn.microsoft.com/en-us/library/930f87yf.aspx https://msdn.microsoft.com/en-us/library/930f87yf.aspx But other common first-party windows development tools can still have the problem: https://github.com/Microsoft/msbuild/issues/53 https://github.com/Microsoft/msbuild/issues/53
  • tracker1 10y ago
    I'm half surprised that wasn't in NT4 (prior to 2000 even)... been a major thing that pissed me off in .Net a couple years ago... "why in freaking 2014 is this still a problem?!?!" Was really happy to see it was finally fixed in .Net and the Anniversary update, and long, long overdue.