> MaxPath
Oh, Microsoft finally woke up and supports path longer than 260 chars in dotNetCore. So, the questions when will Microsoft WinAPI & and the Windows Shell/Explorer too? Will we probably have for Windows 11...
Oh, Microsoft finally woke up and supports path longer than 260 chars in dotNetCore. So, the questions when will Microsoft WinAPI & and the Windows Shell/Explorer too? Will we probably have for Windows 11...
[0]: https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
We do hear about this limitations on Windows somewhat frequently in the context of .NET. This comes from internal Microsoft teams about as much as anyone else. We were glad to remove this limitation for .NET Core.
Disclosure: .NET Team member
Have a TFS build server that puts your cloned projects at not-the-top-of-the-filesystem.
It's very easy to hit that limit. It's atrocious and a joke. And Microsoft has paid me as an employee to write some ridiculous stupid workarounds for it in completely 100% managed C# code that shouldn't be bound by such stupid legacy decisions.
I hate MAX_PATH with a passion. It's one of those things that basically forces a hacky solution every, god, damn, time.