News for hackers. Stuff that matters.

A comment on .NET Framework 4.6.2. Parent comment

Re:.NET Framework 4.6.2 by dogma1138 on Tuesday August 02, 2016 @06:16PM (#12213859)
Yes it was originally the same as the UNC path limit which was 260 chars. Microsoft (a while ago) has updated WinAPI to support unicode and under extended-length paths has lifted the limit up to 32,767 chars it seems that now .NET matched this also. https://msdn.microsoft.com/en-us/library/aa365247(VS.85).asp...
[ Parent | on HN ]
Re:.NET Framework 4.6.2 by poizan42 on Wednesday August 03, 2016 @03:40AM (#12216316)
"A while ago"? That was at least back in NT 3.5
[ Parent | on HN ]
Re:.NET Framework 4.6.2 by dogma1138 on Wednesday August 03, 2016 @06:14AM (#12216903)
IIRC the MAX_PATH limit was lifted from Win32 with one of the Windows 10 builds. But it's true that unicode support was there for a "while" ;) the limit however was still enforced, so I should've been more clear that only the restriction lifting was more recent than 2 decades past.
[ Parent | on HN ]