Long path support in Net.Framework 4.7.2 and Windows 10

Asked May 25 '20 at 22:33

Active May 25 '20 at 22:33

Viewed 1,746 times

To solve the problem of limiting paths to 255 characters, the following was done:

Windows 10 2004 includes "Enable Win32 long paths" in the "Local Computer Policy".
In the registry branch: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ FileSystem set LongPathsEnabled = 1
Created a project in VS (Net.Framework 4.7.2)
Added manifest file (app.manifest) including longPathAware.
The fragment <AppContextSwitchOverrides value = "Switch.System.IO.UseLegacyPathHandling = false; Switch.System.IO.BlockLongPaths = false" /> is added to App.Config

But PathToLong exception still occurs when working with System.IO

asked May 25 '20 at 22:33

Merkurius

maybe the manifest is invalid and the longPathAware entry is added at wrong place – magicandre1981 May 26 '20 at 14:30
As indicated in the source https://learn.microsoft.com/ru-ru/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN ``` true ``` – Merkurius May 27 '20 at 18:03
have you also added the [supportedOS entry for Windows10](https://learn.microsoft.com/en-us/windows/win32/sbscs/application-manifests#supportedos) to manifest? – magicandre1981 May 28 '20 at 13:31
Added only Windows 10. This does not work. – Merkurius May 29 '20 at 22:09
try .net 4.8 as it is latest classic .net framework version, .net 5 will be .net core based. – magicandre1981 May 30 '20 at 07:37
Does not allow to install 4.8, writes that it is already installed. But in the project properties, the highest available version is 4.7.2 – Merkurius May 30 '20 at 18:10
You need to run Visual Studio installer and select 4.8 target pack – magicandre1981 May 30 '20 at 18:26
No. With 4.8 It also did not help. But they write that there is support for long paths since version 4.6.2 and higher – Merkurius May 30 '20 at 20:38

0 Answers0