Today is a quick post day. Do you remember that Windows 10 finally add support to work with long paths? (MAX_PATH) So, with the release of .Net Framework 4.6.2 we also have support to fix this issue from a developers view, I mean working with System.IO.
The post with the new features on .Net Fwk 4.6.2 explains some additional details on how to update an app to take advantage of this new feature.
We fixed the 260 character (MAXPATH) file name length limitation in the System.IO APIs. Over 4500 of you voted for this issue on UserVoice!
This limitation doesn’t usually affect consumer applications (for example, loading files out of “My Documents”), but is more common on developer machines that build deeply nested source trees or use specialized tools that also run on Unix (where long paths are much more common).
This new capability is enabled for applications that target the .NET Framework 4.6.2 (or later).
Greetings @ Toronto
- Windows 10 – Path too long, not anymore !!! (Goodbye to 256 chars restriction)
- Announcing .Net Framework 4.6.2