The issue will be always present in Windows, to keep compatibility with old software. Use the NT-style name syntax "\?D:very long path"
to workaround this issue.
In Windows 10 (Version 1607 - Anniversary Update) and Windows Server 2016 you seem to have an option to ignore the MAX_PATH issue by overriding a group policy entry enable NTFS long paths
under Computer Configuration
-> Admin Templates
-> System
-> FileSystem
:
The applications must have an entry longPathAware
similar to DPIAware in the application manifest.
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" >
<asmv3:application>
<asmv3:windowsSettings xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
<longPathAware>true</longPathAware>
</asmv3:windowsSettings>
</asmv3:application>
</assembly>
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…